-
Notifications
You must be signed in to change notification settings - Fork 844
PROXY Protocol transformed to Forwarded HTTP header #3958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I'm working with the code and one thing I wonder is, why is the proxy protocol map in |
|
A bit more work. Here's a diff that seems to work to have |
|
@SolidWallOfCode This is not only for SSL/TLS requests. It was written to work for both HTTP and HTTPS. If we only want it to work for HTTP, we can just config it in the SSLConfigParams and be done with it. I have a working callback already written where HttpConfig calls into an SSLConfigParams config_init function, but when HttpConfig calls to set the IpMap reference the SSLConfigParams doesn't exist and there is nothing for HttpConfig to write into. |
|
Ah. However, I don't see the problem concerning the |
e2814f7 to
ef785f2
Compare
654f179
951bcb8 to
654f179
Compare
654f179 to
a9ab891
Compare
|
[approve ci autest] |
This update adds a port descriptor option for enabling Proxy Protocol as well as a whitelist of trusted IP addresses as sources of incoming requests with Proxy Protocol headers. If the the Proxy Protocol is enabled and the PROXY header is prefaced on an incoming request, the remote address is changed internally to reflect the original client IP. This has the side effect of transforming the originating IP address into the Forwarded: header for: field, if proxy.config.http.insert_forwaded is configured with the for: field. This will also facilitate logging of the proper client IP versus the previous hop address, i.e. load balancer.