tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: POST request with timeout acts weird
Date Mon, 05 Oct 2009 13:22:24 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

André,

On 10/5/2009 8:41 AM, André Warnier wrote:
> - but, internally and undocumented, Tomcat also uses the same
> "connectTimeout" timeout value when it is subsequently asked to read the
> request body (for example with getParameters()).  But since the
> getParameters() method, (as per the Servlet Spec I guess) does not allow
> for a timeout exception to be returned, Tomcat merely returns an empty
> parameter map when this timeout occurs.

I wonder if a partial parameter map would be returned if /some/ POST
parameters were sent, but the Content-Length was never satisfied (and
this timeout occurred).

> It appears that there is no way to explicitly set (individually) the
> timeout for reading the request body, nor to get a specific error when
> whatever timeout is being used, is exceeded.

The servlet API does not appear to support this.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrJ8w8ACgkQ9CaO5/Lv0PAmagCgqwpH4x9sam8CK4BoqG/hy+9A
R94An3ns68z6ZPg4L5xbKxgdwxTgOe/E
=k52B
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message