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. It isn't a big deal though as our front facing Apache HTTP server does return 414, I just wanted to make sure my testing was thorough.
I didn't realize the large amount of time between the point releases; unfortunately the .14 release is included by default on our dev machines. Thanks again for the help. Christopher Schultz-2 wrote: > > > So, it looks like Tomcat just closes the connection in that case. > > That's not particularly helpful, unfortunately. The fact that you're not > getting a timeout is useful, though. > > Would you mind upgrading to the latest 6.0.x release (it's currently > 6.0.26... your version is nearly 3 years old) and trying again? If this > problem still exists, you'll need to upgrade to get a fix for it, anyway. > > - -chris > > -- View this message in context: http://old.nabble.com/URL-Exceeding-maxHttpHeaderSize-tp28687322p28700228.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
