SECURE_PROXY_SSL_HEADER Example in Documentation Should Use X-Forwarded-Proto Instead of X-Forwarded-Protocol
|Reported by:||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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:
There is also a wikipedia article mentioning the same thing (albeit not the bible):
I would like to see the documentation perhaps reflect the state of things most common in the working world if possible.