-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 12/14/2010 5:05 AM, André Warnier wrote: > Klemens Muthmann wrote: >> Didn't know this. I thought files would be part of the message content. > > Well, in a well-behaved application using HTTP, they should be. > HTTP headers are generally meant to convey information /about/ the > content, not to /be/ the content. Otherwise they would not be called > HTTP headers. > > To be more clear : if your REST application is sending content in the > HTTP headers, then it is not a well-behaved HTTP application. > Tomcat is on the receiving end, and it is primarily a HTTP server. It > tries to do its best to digest what clients throw at it, but it is not > normally expecting to receive HTTP headers of that size. The quick fix > which Mark gave you, is only that. The problem is with your application. If AJP is involved (via mod_jk or mod_proxy_ajp) then there is another header size that needs to be increased: the first AJP packet sent to Tomcat must contain the entire request headers -- I'm not exactly sure why this is the case -- and if it doesn't, bad things can happen. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0HllYACgkQ9CaO5/Lv0PAhDgCgj1AOUgJGgu3KgeWCdrYtxrVm LKsAoJUrwxGAyJdLESjnUzDWrEhCsrIH =6cOv -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
