Greetings,
Trunk can log connection source port by using in Logformat : "%{remote}p".
2.2 currently does not support that (only logs the destination port of
the connection).
Included is a very simple (trivial) backport of that functionnality from
trunk to 2.2.
Tested, works for me.
Vincent
I am the developer of FirePHP (http://www.firephp.org/) which is a
debugging tool for PHP. It allows you to print debug messages from PHP
on the server to the Firebug (http://www.getfirebug.com/) Console. It
sends the debug data in the response headers instead of the response
body so that page rend
>>> On 4/14/2008 at 3:29 PM, in message <[EMAIL PROTECTED]>, Chris
Darroch <[EMAIL PROTECTED]> wrote:
> Brad Nicholes wrote:
>
>> This is where it starts to go wrong for me. Where it gets confusing
>> for somebody who is trying to figure out what the configuration
>> is doing is:
>>
>>
>>
Brad Nicholes wrote:
IOW, we may be required to be conservative when it comes to 1.3.x, 2.0.x
or 2.2.x,
s/be required/desire/ - it's a group consensus. It wasn't this way prior to
the 2.0.43 and doesn't have to be that way in the future, but I think it has
served our users well, and hasn't