William Edwards

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/,...

Hi, When using the QS_ClientIpFromHeader directive, mod_qos returns: mod_qos(069): no valid IP header found (@hp): header 'X-Forwarded-For' not available, fallback to connection's IP 10.40.23.9 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. <IfModule mod_qos.c> QS_LogOnly...