-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom,
On 4/12/2011 4:22 AM, Tomislav Brkljačić wrote: > After that i added the whole spring distro, ran the test scenarios and > didn't find any problems. I guess if that works.... I just think it's unnecessary because you can use a filter from somewhere else (Tomcat, for instance). > Christopher Schultz-2 wrote: >> >> I don't think you want this: you only want to set the encoding when the >> client has provided none. If the client provides an encoding and you >> override it, you are probably making a bit mistake. > > I see. > The app i'm building will be accessible on intranet only. > Guessing on what can a client send as attach is not wise, i know. > > Could this issue be handled with a smarter custom filter in place of the > generic one ? Just set forceEncoding=false (or don't set it at all: the default /should/ be not to force the encoding because it's a bad idea). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2kW/wACgkQ9CaO5/Lv0PBriwCfYsjBk1b5YWGGKLYUDghs4ESW MmMAniI9+VHADDcznoZy2JWVY6qqsn/x =wA6L -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
