-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
X-Real-IP and X-Forwarded-For missing #800
Comments
I am working in adding e2e test to the ingress controller in order to avoid all this regressions we are having. #801 |
I believe this is the change that caused the issue. If you set |
I am using |
@weitzj negative, I can't confirm that. I tried, and passing |
@totallyunknown please update the image to quay.io/aledbf/nginx-ingress-controller:0.148 |
Closing. Please reopen if you still have issues |
Thanks. It's working with quay.io/aledbf/nginx-ingress-controller:0.148. But it looks like, the fix is not included in 0.9.0-beta-9? |
The fix is in master https://github.com/kubernetes/ingress/blob/master/controllers/nginx/rootfs/etc/nginx/template/nginx.tmpl#L138 and included in the PR for 0.9.0-beta-9 |
PR #905 |
Thanks, I've took a look into the Changelog and #890 isn't listed - that why I was asking. |
@totallyunknown sorry, the issues are not sorted https://github.com/kubernetes/ingress/pull/905/files#diff-2b00570d6a55cbb418bfb30203d59114R25 |
I've upgraded from 0.9.0-beta5 to beta 7 and I don't see any X-Real-IP or X-Forwarded-For-Header anymore.
beta5:
beta 6/7:
SSL is terminated by an AWS ELB. No proxy protocol is used.
The text was updated successfully, but these errors were encountered: