-
Notifications
You must be signed in to change notification settings - Fork 8
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
Miss remoteip module #21
Comments
Adding this wouldn't be too difficult I guess, but I wonder why you need it. DokuWiki already recognizes the proxy headers and properly uses the origin IP when logging etc. So what's the rationale behind this request? |
You can start with the logs of the container, in the current form there is no real ip address of the client, only docker subnets:
In addition I use the yourip plugin, which also doesn't work without this module. |
Hi there. I've discovered that enabling apache's remote ip module breaks the Also, is it |
fuck. so far for the testing by @avbor. gonna have a look later. Will probably revert. |
Reverted in 52a48fd If someone can come up with a good solution to the issue, PR would be welcome. |
I set |
That is certainly not the ideal solution. |
Hi.
Despite the fact that this container is “It is meant to be used with a reverse proxy” there is no Apache remoteip module loaded in the container =)
It would be great to enable it by default.
(
something like:
a2enmod remoteip
echo "RemoteIPInternalProxy 172.16.0.0/12" >> /etc/apache2/conf-enabled/remoteip.conf
echo "RemoteIPHeader X-Forwarded-For" >> /etc/apache2/conf-enabled/remoteip.conf
or pass RemoteIPInternalProxy and RemoteIPHeader from env
)
The text was updated successfully, but these errors were encountered: