-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom,
On 4/8/2011 11:42 AM, Tomislav Brkljačić wrote: > The remote machine gives the wrong "result". Okay. Could you post a LiveHttpHeaders dump of /that/ interaction, too? > 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 . Tomcat's examples come with a filter that does exactly this. It's called SetCharacterEncodingFilter and it can be found in the "examples" webapp. We always run with such a filter in place because it solves all kinds of problems with POST requests. My initial reaction was that the headers are not part of the request body, so the SetCharacterEncodingFilter wouldn't have an effect, but then again, the request body contains the multipart/form-data including the headers of each multipart part. This may solve all your problems. Let us know how it goes. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2fLtkACgkQ9CaO5/Lv0PBa9QCgqSihhlwnMH4c4nqpN9HP2ACX iLMAn3B2P5u/qT4ipH6xaR+LbycTJ4gI =oiLZ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
