Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Override 'wsgi.url_scheme' via a request header, 'X_WSGI_URL_SCHEME'. #42
referenced this pull request
Oct 24, 2013
This should be opt-in, and should also include the
@mmerickel @sontek : 'X-Forwarded-For' isn't relevant to this PR, which is about allowing mixed-mode proxies to signal to the application which scheme was used in the original request, so that they can generate absolute URLs using the same scheme.
But yes, I haven't merged this because of the concern @mmerickel mentions about folks running w/o proxies.
I wish this was done via the
added a commit
this pull request
Mar 10, 2014
Huh, I just followed the latest documentation and hadn't realised that this isn't released yet. Surprised such a feature is so new. What's the best way to configure it before the new release, then?
With respect to the issue at hand, what if there are multiple proxies in a load balancing arrangement? It seems like hard-coding IPs into application configuration files is not the ideal place to do it and that this configuration should really live in the runtime environment architecture or in a firewall. If I was deploying an application I would make it listen on an interface where only trusted proxies could talk to it in the first place.