Why? I can confirm that X-Forwarded-For is present. In fact, mod_remoteip uses it successfully (and I would expect mod_qos to honour it, but that's a different matter).
The full config can be found below, although I can reproduce the issue when using the directive standalone.
I'm on version 11.63. I am aware that is not the latest, but it is the version currently shipped for Debian stable, and the changelog (https://mod-qos.sourceforge.net/CHANGES.txt) doesn't mention any related fixes/changes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I missed that nuance in the documentation. Sorry about that, and thanks for finding it.
If mod_remoteip removes X-Forwarded-For, there are no headers containing the IP address (I could let the proxy add a header, but I'd rather not). And without QS_ClientIpFromHeader, mod_qos (rightly) believes the connection comes from the proxy.
I agree: mod_remoteip got fully integrated into Apache as of version 2.4.19... it's time for mod_qos to adapt and also support Apache's "useragent_ip" feature.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
When using the QS_ClientIpFromHeader directive, mod_qos returns:
Why? I can confirm that X-Forwarded-For is present. In fact, mod_remoteip uses it successfully (and I would expect mod_qos to honour it, but that's a different matter).
The full config can be found below, although I can reproduce the issue when using the directive standalone.
I'm on version 11.63. I am aware that is not the latest, but it is the version currently shipped for Debian stable, and the changelog (https://mod-qos.sourceforge.net/CHANGES.txt) doesn't mention any related fixes/changes.
I assume mod_remoteip is causing the problem.
https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html
mod_remoteip.c:
Hi @pbuchbinder,
I missed that nuance in the documentation. Sorry about that, and thanks for finding it.
If mod_remoteip removes X-Forwarded-For, there are no headers containing the IP address (I could let the proxy add a header, but I'd rather not). And without QS_ClientIpFromHeader, mod_qos (rightly) believes the connection comes from the proxy.
Are you familiar with successful mod_qos + mod_remoteip approaches? mod_remoteip is not a very exotic module. I found https://sourceforge.net/p/mod-qos/discussion/697421/thread/96040e61/, but that's a dead end.
I agree: mod_remoteip got fully integrated into Apache as of version 2.4.19... it's time for mod_qos to adapt and also support Apache's "useragent_ip" feature.
mod_qos version 11.75 is now available.
It uses the IP address determined by mod_remoteip by configuring