-
Notifications
You must be signed in to change notification settings - Fork 686
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
Proxy Protocol Causes Issues with Cleartext Redirection in 0.50.0 #1115
Comments
Update. If you are terminating TLS at the ELB, setting the Ambassador logs this access log: |
Quick update, this fails because |
Can confirm. This has been fixed on |
Thanks :) |
Leaving in "done" instead of "closed" because we haven't shipped it yet... |
Fixed in RC6 |
This is still not working for me in 1.9.1. All http:// requests get a 404, while all https:// ones work. Mapping:
Host:
curl request:
Ambassador log line:
Match from diag screen:
|
Describe the bug
When enabling http -> https redirection in the tls module with
redirect_cleartext_from: 80
, there appears to be an issue that comes up whenuse_proxy_proto: true
is set in the ambassadorModule
and the LB is enabling proxy protocol.HTTPS requests work perfectly fine but http requests return a 400 instead of a 301 redirect to https.
To Reproduce
use_proxy_proto: true
in ambassadorModule
:redirect_cleartext_from: 80
:When you remove
service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*"
anduse_proxy_proto: true
, http redirects correctly.Versions (please complete the following information):
Additional context
This has existed in all versions of 0.50.0
The text was updated successfully, but these errors were encountered: