-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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-Forwarded-For header #2762
Comments
Laravel supports this already: |
Thanks for the suggestion @sorano, |
Well, I havent actually been looking "within" bookstack. The apache vhost configuration has:
So I'm looking at access.log and seeing log entries like these:
Where 172.25.0.124 is the IP of the reverse proxy. However I guess logging within the application would be needed to show the real IP since apache access would be processed before. |
@sorano I don't think we'd have any control over what apache is logging in that regard. You'll likely need to alter the LogFormat like so: Or maybe attempt using mod_remoteip? |
Will therefore close this off. If you're sure that BookStack determines any IP address you see then feel free to comment with any evidence and I'll reopen this. |
I faced the same issue: Reverse Proxy IPs where shown in the apache and bookstack audit logs. Solved it with the apache module remoteip. Now real client ips appear in apache and audit logs. Enable module:
Add config
Restart Apache
|
Describe the feature you'd like
It would be nice to support the X-Forwarded-For header
Describe the benefits this feature would bring to BookStack users
When hosting bookstack behind a reverse proxy any login will show the IP from the reverse proxy instead of the IP of originating user. For trackability and identification it would be nice to see the real IP.
Additional context
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For
The text was updated successfully, but these errors were encountered: