Just to confirm, it is a bug in the InputBuffer, not OutputBuffer?
Yuesong
On Jan 21, 2011, at 6:12 AM, Mark Thomas wrote:
On 21/01/2011 00:53, Yuesong Wang wrote:
Hi,
Is there a reason why InternalNioInputBuffer automatically grows its buffer,
effectively ignoring the maxHttpHeaderSize
So the bug is InternalNioInputBuffer not honoring maxHttpHeaderSize?
Yuesong
On Jan 21, 2011, at 9:33 AM, Mark Thomas wrote:
On 21/01/2011 13:55, Yuesong Wang wrote:
Just to confirm, it is a bug in the InputBuffer, not OutputBuffer?
InputBuffer, yes.
OutputBuffer not so sure
Done:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50631
Thanks,
Yuesong
On Jan 21, 2011, at 9:33 AM, Mark Thomas wrote:
On 21/01/2011 13:55, Yuesong Wang wrote:
Just to confirm, it is a bug in the InputBuffer, not OutputBuffer?
InputBuffer, yes.
OutputBuffer not so sure
Thanks. I tried 6.0.30, but under heavy load in our production environment, its
memory usage shot up in a matter of minutes and we had to bring it down. We did
not see that in 6.0.29.
Yuesong
On Jan 19, 2011, at 5:59 PM, Mark Thomas wrote:
On 19/01/2011 19:54, Yuesong Wang wrote:
Hi,
I
: Yuesong Wang
Sent: Thursday, January 20, 2011 10:41
To: Tomcat Users List
Subject: Re: Request Line Truncated and Caused 501
Thanks. I tried 6.0.30, but under heavy load in our
production environment, its memory usage shot up in a matter
of minutes and we had to bring it down. We did
Hi,
Is there a reason why InternalNioInputBuffer automatically grows its buffer,
effectively ignoring the maxHttpHeaderSize setting, while
InternalNioOutputBuffer doesn't? I was playing around with the setting, and set
it to a rather small value. While large requests seem to go through without
Hi,
I have tomcat 6.0.29 configured using the NIO connector running on linux. My
access log shows strange 501 errors like this:
86.24.156.114 - - [19/Jan/2011:14:41:28 -0500] eferer: /static/r07/sh30.html
501 1235 - -
41.203.64.251 - - [19/Jan/2011:14:39:18 -0500] ET actual url HTTP/1.1 501
