On 21/01/2011 00:53, Yuesong Wang wrote:
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.
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
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. As a minimum, it should be consistent with the
other connectors. I haven't checked how they behave.
Mark
Yuesong
On Jan 21, 2011, at
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. As a
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. As a
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
