-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Proxy protocol support #10645
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
Comments
We don't have plans to add something like this to the server. Our current recommendation is to use the |
Note for 3.0 we're adding support for client certificates forwarded in headers (and then using them for authentication). #9756 |
@anurse XFF header cannot be injected into encrypted traffic. If we terminate SSL earlier, service will not be able to performe Mutual TLS as SSL is already offloaded. @Tratcher That is nice but it requires to have some other services in a front of our service who can get client certificate and put it in defined http header. Is there any other solution? |
Terminating SSL on NGinx and forwarding the client cert and IP is your best option. |
Thanks @Tratcher! |
Is your feature request related to a problem? Please describe.
I have Kubernetes Cluster with NginX Reverse proxy in a front of worker nodes. Some of my services require Mutual TLS and I setup SSL Pass-trough on NginX Reverse proxy and on Kubernetes Ingress Controller (also NginX). When request hits my services (Kestrel web server), remote (source) IP is IP address of Kubernetes Ingress Controller but not original client IP. It creates me a problem as I need to check ACL based on client IP address. Enabling proxy protocol on both of NginX services I'm able to deliver original client IP to Kestrel but Kestrel at the moment doesn't know to speak proxy protocol in order to get original client IP.
Describe the solution you'd like
I would like to see proxy protocol support for Kestrel web server.
Describe alternatives you've considered
As service itself needs to to Mutual TLS, I see no alternatives for this problem.
Additional context
https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt
Thanks!
The text was updated successfully, but these errors were encountered: