tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Kolinko <knst.koli...@gmail.com>
Subject Re: Logging properties of attributes in the HttpSession
Date Fri, 30 Sep 2011 18:18:25 GMT
2011/9/30 Christopher Schultz <chris@christopherschultz.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Konstantin,
>
> On 9/30/2011 9:27 AM, Konstantin Kolinko wrote:
>> 2011/9/30 André Warnier <aw@ice-sa.com>:
>>> Pid * wrote:
>>>>
>>>> The changes from the Spring security filter can't be seen by
>>>> the access log valve.
>>>>
>>> And is the "why?" left as an exercise to the reader ?
>>>
>>
>> Because logging happens after request processing is completed, and
>> a filter affects only what happens "inside" the filter in the
>> request handling chain.
>>
>> The filter wraps request, but log valve sees the original unwrapped
>> request.
>>
>> If you need to pass this information to the log valve, I'd suggest
>> you to assign it to a request attribute.
>
> The OP should be able to put the Filter into the <Context> in such a
> way that the Filter wraps the AccessLogValve, no?
>

1. You cannot put a Filter into Context.
2. AccessLogValve in Tomcat 7 cannot be wrapped. It does not act as a
true "valve", but more as a marker interface.

3. A Valve can modify a Request, while Filter cannot.

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message