Access log - Default format is not consistent with documentation (missing "X-Forwarded-For" header) #2114
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/documentation
Categorizes issue or PR as related to documentation.
Is this a request for help? : No, it's a bug report.
What keywords did you search in NGINX Ingress controller issues before filing this one? :
Is this a BUG REPORT or FEATURE REQUEST? : BUG REPORT
NGINX Ingress controller version:
0.10.2
Kubernetes version :
Environment:
uname -a
):What happened:
Access log format is not consistent with the documentation.
According to the documentation (ingress-nginx/docs/user-guide/log-format.md), the information between the first brackets should be "[$proxy_add_x_forwarded_for]" but it is "[$the_real_ip]".
Thus, some information are lost when the Ingress Controller is behind another reverse proxy.
What you expected to happen:
According to the documentation (ingress-nginx/docs/user-guide/log-format.md), the information between the first brackets should be "[$proxy_add_x_forwarded_for]".
How to reproduce it:
Look at the generated nginx.conf file:
I expected that the returned line whould be:
Anything else we need to know:
I think the fix should be done in the file
ingress-nginx/internal/ingress/controller/config/config.go
, changing the line :by
The text was updated successfully, but these errors were encountered: