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
Add support for X-Forwarded-For #26
Comments
That code isn't commented out. It is a preprocessor directive. For 2.2, you can use a backported version of mod_remoteip such as mod_remoteip-httpd22, which is what we use in our unit tests, or something like mod_rpaf may work as well. |
Oh sorry, I am not familiar with c. Thanks, I will check the links and respond later. mod_rpaf sounds really promising. |
This feature was added in mod_geoip2 , including a feature we requested, "GeoIPUseFirstNonPrivateXForwardedForIP". We would like to stop using the "Legacy" MaxMind DB's, but would also prefer not to have this "regression". https://github.com/maxmind/geoip-api-mod_geoip2/blob/master/mod_geoip.c#L388 |
Is there a reason why you can't use |
Closing as |
Hi,
in your description it says:
However, the still wildly used Apache 2.2 doesn't include mod_remoteip.
I also see in your code:
You tried to support both but the condition are commented out.
Could you please add support for 2.2 in this regard? Especially it would be cool if there were a config setting so that the module uses the client ip coming from the X-Forwarded-For header.
What do you think? We tried using a downgrade version of mod_remoteip which initially worked, but gives us SIGTERMs.
We would like to use a commercial license from you, but this technical issue is blocking us right now.
Thanks,
Daniel
The text was updated successfully, but these errors were encountered: