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
Here is my connector configuration:
I'm using Tomcat 6.0.14
The connection doesn't hang but the reply is empty. Here is the detailed
output from cURL:
* Empty reply from server
* Connection #0 to host localhost left intact
curl: (52) Empty reply from server
* Closing connection #0
I tested
I'm running tests against a web app running in Tomcat and I was asked to test
extremely long URL query strings. I've read servers should throw HTTP
status 414 if the header size is too long however whenever I make the call
to Tomcat there is no response; ideally I would like it to return a 414
er
