#19246: SECURE_PROXY_SSL_HEADER Example in Documentation Should Use X-Forwarded-
Proto Instead of X-Forwarded-Protocol
-------------------------------+--------------------
Reporter: fred.palmer@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.4
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
While setting up a reverse proxy scenario with nginx and AWS I noticed the
documentation uses an example (while technically correct) is somewhat off-
kilter from emerging de-facto standards for the header in question.
For example - the Elastic Load Balancer uses:
http://docs.amazonwebservices.com/ElasticLoadBalancing/latest/DeveloperGuide
/arch-loadbalancing.html#x-forwarded-proto
There is also a wikipedia article mentioning the same thing (albeit not
the bible):
http://en.wikipedia.org/wiki/List_of_HTTP_header_fields
I would like to see the documentation perhaps reflect the state of things
most common in the working world if possible.
--
Ticket URL: <https://code.djangoproject.com/ticket/19246>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
