SECURE_PROXY_SSL_HEADER Example in Documentation Should Use X-Forwarded-Proto Instead of X-Forwarded-Protocol

[fred.palmer@…]

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.

[Tim Graham]

Fixed in 2cc1884383a0b5371854be6806851521b623f45b