-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 Tom
l 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.
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
On 5/27/2010 1:37 PM, glau_pldm wrote:
> connectionTimeout="2"
>redirectPort="8443"
>maxHttpHeaderSize="8192" />
>
> I'm using Tomcat 6.0.14
>
> The connection doesn't hang
trying to send? An example would really
> help. So would your exact version of Tomcat.
>
> Can you post the rest of your configuration, too?
>
> - -chris
>
>
--
View this message in context:
http://old.nabble.com/URL-Exceeding-maxHttpHeaderSize-tp28687322p28697519.ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
On 5/26/2010 6:31 PM, glau_pldm wrote:
> 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
turn a 414
error. I have my http connector configured with maxHttpHeaderSize="8192"
--
View this message in context:
http://old.nabble.com/URL-Exceeding-maxHttpHeaderSize-tp28687322p28687322.html
Sent from the Tomcat - User mailing list a
