- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 223
Open
Description
In looking at func scheme() I see we do some auto detection for X-forward-for,   This header is considered non-standard though its use is fairly ubiquitous.
X-Forward-For has been superseded by RFC7239. It would probably be well served to implement support for that as well. Haproxy will set this header properly when options forwarded is add to the relevant haproxy backend section of the configuration. The go-forward package  makes handling both X-Forward-* and forwarded headers easy.
Originally posted by @dBitech in #994 (comment)
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Ready