-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 To whom it may concern,
On 5/27/2010 5:45 PM, glau_pldm wrote: > Thanks for the help. Using the latest release fixed the empty response; it > doesn't return a 414 but at least it now returns a 400 bad request. Would you mind filing a bug against Tomcat? It really should be returning 413 or 414 as appropriate. Can you write a test that should generate a 414 (with a huge Request-URI) and one with more than maxHttpHeaderSize bytes (obviously, you can set this to something semi-low to trigger it), say, by sending lots of headers? Thanks, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv/yeMACgkQ9CaO5/Lv0PCU7wCfSZcGDI7MVjclUUDlQWVMFndJ 2eQAoKCPOhjvZzp/pkz1lJgEUU6TBLhS =iv3A -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
