Chris,

2010/12/27 Christopher Schultz <ch...@christopherschultz.net>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Olaf,
>
> On 12/27/2010 5:02 PM, Olaf Tomczak wrote:
> > 2010/12/27 André Warnier <a...@ice-sa.com>
> >> I believe that in the default configuration, Tomcat expects to read the
> >> request line *and all the headers* in the first read of maximum 8000
> bytes.
> >> The cookies are part of the headers.
> >>
> >> Increase the maxHttpHeaderSize attribute to cover the headers of the
> >> largest likely request and see what happens ?
> >
> > I did not increase this attribute, although I don't think my request was
> > larger than 1500 bytes.
>
> Please check. Can you post your test case?
>
> > Besides I thought that the whole idea of non-blocking connector is
> > that it doesn't have to read the whole request at once - isn't that
> > what blocking connector does?
>
> Non-blocking just means that your request processor threads don't block
> waiting for data to arrive. The requirements of reading the request --
> including all the headers -- do not change with the connector. Tomcat
> needs to read the entire set of headers in order to route the request to
> the right host and webapp. Also, Tomcat must have all headers in order
> to perform some operations -- such as responding to "getHeaders" calls
> which sometimes require that multiple separate HTTP header lines be
> merged into a single method return value.
>

I understand that the whole request must be read to start "request
processing" - I was just suggesting that from what I understand the
connector does not wait for the buffer to be completely filled before
starting to parse request line and headers. Isn't that right?

Thanks, Olaf

>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk0ZD3AACgkQ9CaO5/Lv0PCqXwCfbuybnLIOtiTLO72/e2OBSkKo
> RFwAoIVXMaXHIrTuVMxoAYpJIsykP8er
> =z0Hx
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Reply via email to