Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Incorrect X-Forwarded-Port for TLS servers #76

Closed
pingles opened this issue Dec 21, 2016 · 0 comments · Fixed by #82
Closed

Incorrect X-Forwarded-Port for TLS servers #76

pingles opened this issue Dec 21, 2016 · 0 comments · Fixed by #82
Assignees
@aledbf
Labels
nginx

Comments

@pingles
Copy link

pingles commented Dec 21, 2016

It appears that the X-Forwarded-Port is set incorrectly when ingress is configured for TLS resources: it looks like it ends up with a value of 442 as a result of the SSL server configuration.

This has the effect of breaking some applications that use the X-Forwared- headers to generate URLs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aledbf aledbf

Labels
nginx
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix incorrect X-Forwarded-Port for TLS aledbf/ingress-nginx
2 participants
@pingles @aledbf