You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That changed nothing. Again, the client's IP is shown.
My Go skills are nonexistent, but I think I figured out, what happens:
We're not even getting to Line 64, because the header is already set and it returns a line earlier. That field is set in Line 32, but it's using the X-Forwarded-For header (which is the client's IP!) and not the X-Forwarded-Host header, which would be correct.
So I think it's a bug in that library, and I wanted to open an issue – but it turns out, it has already been open for more than half a year: gin-contrib/location#15 😞
Closing, as this has to be fixed upstream.
EDIT: Wow, the fix was proposed even earlier and rejected because "it would be a breaking change": gin-contrib/location#13 😠
EDIT2: So yeah, the info page gets rendered correctly if I remove the X-Forwarded-For header. However, then the clientIP in the logs is of course no longer correct...
I'm using chartmuseum in a Docker container behind a reverse proxy.
I've set the
--chart-url
option, so the generated URLs in theindex.yaml
are correct.However, the info page (when accessing the domain with a browser) shows the client IP instead:
It would be nice to have the URL in there also customizable.
Thanks!
The text was updated successfully, but these errors were encountered: