[users@httpd] RemoteIPInternalProxy / RemoteIPTrustedProxy

2017-12-18 Thread David Tkacik
Hi, I'm using the RemoteIPHeader X-Forwarded-For within a VirtualHost configuration in order to determine GEO location of our users within our PHP application. But I also would like to log the Remote IP of the clients within the apache logs. The Apache combined log format looks like this: L

Re: [users@httpd] RemoteIPInternalProxy / RemoteIPTrustedProxy

2017-12-18 Thread Eric Covener
> BUT, when I set this Apache stops logging the remote IP because the > forwarding proxy is valid now ? > LogFormat "%h (%{X-Forwarded-For}i) %l %u %t \"%r\" %>s %b \"%{Referer}i\" > \"%{User-Agent}i\"" combined You should restore %a to that format if you're going to use mod_remoteip. As was ex

Re: [users@httpd] RemoteIPInternalProxy / RemoteIPTrustedProxy

2017-12-18 Thread David Tkacik
Eric, Thanks a lot for your answer. David > On 18 Dec 2017, at 13:57, Eric Covener wrote: > >> BUT, when I set this Apache stops logging the remote IP because the >> forwarding proxy is valid now ? > >> LogFormat "%h (%{X-Forwarded-For}i) %l %u %t \"%r\" %>s %b \"%{Referer}i\" >> \"%{User-A

[users@httpd] SSI/website rendering errors

2017-12-18 Thread Joel Miller
I thank both of you for your responses. I was simply trying to determine if similar issues had arisen with Apache - I didn't expect a resolution for a LiteSpeed problem. As it turns out, LiteSpeed rolled out an update last evening which fixed the SSI errors. -