gt; To: Tomcat Users List
>> Subject: Re: AccessLogValve calling order
>>
>> Hi Chris.
>>
>> Thanks for diagnosing this problem! It appears you're right that it
>> logs
>> only after the session is invalidated (after the request is complete)
>> on a
ce.com]
> Sent: Friday, November 13, 2009 7:12 PM
> To: Tomcat Users List
> Subject: Re: AccessLogValve calling order
>
> Hi Chris.
>
> Thanks for diagnosing this problem! It appears you're right that it
> logs
> only after the session is invalidated (after the reques
Hi Chris.
Thanks for diagnosing this problem! It appears you're right that it logs
only after the session is invalidated (after the request is complete) on a
logout request. That bug has existed in the code for a very long time,
unnoticed. The AccessLogValve was initially implemented to log onl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Amazingly enough, I had my first need to use AccessLogValve today, and
one of the things I wanted to print was the user's session id. No,
problem: just add "%S" to the log pattern.
Well, there is one problem: you can't spit-out the session id fo
