[solved] Allow VH to Inherit Server logFormat Setting

[Atticus]

Hi there!

I am running Litespeed 4.1 Gold in a load balanced environment. While the load balancer supplies the remote client IP address in its own header, Litespeed logs using the default Remote Host header which is that of the load balancer. This makes the standard combined format logs pretty useless in way of tracking requests.

The solution for individual virtual servers is pretty simple. Change the logFormat and include the alternate HTTP header. This is not so simple if you need to update the XML files of 200+ virtual hosts.

Would it be possible to have an option to enable all virtual hosts to adopt the logFormat used by the server configuration?

Thank you!

[mistwang]

http://www.litespeedtech.com/docs/we...pInProxyHeader

[Atticus]

Except X-Forwarded-For is not the header presented making that not so helpful.

[webizen]

http://www.litespeedtech.com/support...hp/t-3896.html

[Atticus]

Set it on the web server side? Litespeed is the web server. Our load balancer uses a header other than X-Forwarded-For making the Client IP Header feature useless. We can't change that. Mind you, we don't use LSLB.

Aside from this one example of different client IP headers, being able to specify a logFormat that is shared by all VH would be supremely beneficial. The method you keep linking me to will not accomplish the need presented.

[webizen]

You can use LogFormat in Server level for VH sharing. X-Forwarded-For header is supported for Apache LogFormat compatibility.

[Atticus]

I set the server-level logFormat and it was not inherited by any of the VHs. Any idea why that may be?

[webizen]

What log format are you using?

[Atticus]

A slightly modified combined format - %{X-Client-IP}i - %h %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i"

[webizen]

pls try with 4.1. it should work.