-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 4/8/2011 11:50 AM, André Warnier wrote: > Tomislav Brkljačić wrote: >> The remote machine gives the wrong "result". >> >> I wrote on the mailing list of the BPM software, the discussion is still >> alive. >> >> Maybe i could try to force a CharacterEncodingFilter filter on tomcat. >> Something like >> http://www.onthoo.com/blog/programming/2005/07/characterencodingfilter.html >> >> this . > > Don't do that. Your problem is with the file *name*, not with the file > content. > Filters work on the content. > I think you could make a real mess of everything by adding a content > filter. I don't think that Tomcat would use it in this case, but if it > does, it will filter the whole multi-part body (headers and contents), > which is certainly not what you want here. If the multipart form-handler uses an InputStream to read the request body, it won't matter what the character encoding is, anyway. I suspect an InputStream will be used, since that is entirely appropriate in this case. On the other hand, setting the character encoding might trigger the multipart parsing library to use the preferred encoding to translate filename bytes into characters. One can dream. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2fMCAACgkQ9CaO5/Lv0PDa8gCfSrZxjxF4vcEcsHkAqFChnYZ4 nsYAni7LNi0PeGjgGGhxxZadvQOh6QuY =VwYO -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
