Opened 2 years ago

Closed 2 years ago

#19246 closed Cleanup/optimization (fixed)

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

Reported by: fred.palmer@… Owned by: nobody
Component: Documentation Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

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.

Change History (2)

comment:1 Changed 2 years ago by claudep

  • Easy pickings set
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted
  • Type changed from Uncategorized to Cleanup/optimization

comment:2 Changed 2 years ago by timo

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.
Back to Top