Do I totally screwed or I read somewhere that we could add some headers to boringproxy?
How would I come to the solution with proxy_set_header X-Forwarded-Proto $scheme;?
I would be also very glad of a boring simple solution for that kind of situation like on Cloudflare services:
Make sure you have working SSL and HTTPS on Heroku (or wherever you’re serving your Rails application.) Turn Cloudflare SSL to Full mode. Problem solved.
There’s no way to set custom headers in boringproxy. I could add it (or add X-Forwarded-Proto explicitly), but I’m not sure when I’d get to it. Can I ask what specifically you need the header for?
After returning on the corresponding project impacted by this issue (my invoice manager), I have noticed that the schema propagation is now perfectly OK.
I guess there must have been some caching somewhere, but in any case everything is fixed and I confirm that the X-Real-IP header is redundant.