-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 4/21/2010 3:20 PM, André Warnier wrote: > Mircea LUTIC wrote: >> Hello Chris, >> > I will save Chris one answer : >> >> 1. If the filter does not influence the decoding of the GET >> parameters why is it called on GET requests? > > Because the filter may want to, for example, modify or add request > headers to the request (or response headers). Or it may want to change.. > the parameters, or rather the request's "query string" as a whole (the > part of the URL after the "?"). > > I think what Chris meant, is that the filter does not influence the way > in which a call like getParameters() works. The standard > getParameters() method takes the request URI (as it sees it by the time > it runs) and parses its query_string part into a table of parameter > names and values, according to fixed rules which you cannot change. (Other than setting the URIEncoding attribute on the <Connector>, of course.) > What your filter /could/ do, is to create a "request wrapper object" > containing the original request. This request wrapper would for example > pass an already-modifed request URI to the getParameters() method. > Or it could re-define the getParmeters() method, to return modified > parameter values. This may or may not work the way you expect it to work. I would recommend lots of testing. :) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvPUwoACgkQ9CaO5/Lv0PC6rACeMcZv4wblmJPHT0ojLl54Mm0T MsMAoKYTIIxlaEL8SV5TaVNGdjFk3Sun =+uD5 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
