-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Konstantin,
On 9/30/2011 9:27 AM, Konstantin Kolinko wrote: > 2011/9/30 André Warnier <a...@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? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6GAF4ACgkQ9CaO5/Lv0PCVGwCfRKafqELtU56KCO4wngj+tPQ8 WXUAn3srp9jQDELhN5xxoGbhRXmQUwPF =Wbqg -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
