RE: [users@httpd] mod_remoteip and ErrorLogFormat

2024-10-30 Thread Gretton, Liam
I am a bit of a muppet. My reason for using mod_remoteip was to be able to get client IPs into the error logs, but I've just discovered that the %i format specifier is available to ErrorLogFormat, so I can use X-Forwarded-For directly there. As mod_remoteip seems to remove X-Forwarded-For as we

RE: [users@httpd] mod_remoteip and ErrorLogFormat

2024-10-30 Thread Gretton, Liam
On 20 October 2024 18:05, Daniel Ferradal Márquez wrote: > What is your "RemoteIpHeader" setting? You have to specify it for > mod_remoteip to work. > > Have you made sure you are getting that header from the front-end with the > correct client ip? RemoteIPHeader is set to X-Forwarded-For. It's

[users@httpd] mod_remoteip and ErrorLogFormat

2024-10-19 Thread Gretton, Liam
httpd 2.4.57-11 on Rocky 9 here. I've been trying to get ErrorLogFormat to log the client IP address rather than that of my proxy's, but it doesn't seem to work. For LogFormat it is working as expected. My suspicion is that mod_remoteip doesn't actually modify core's %a format string, yet the