-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
> the servlet specification defines Content-Length as an int. even
> though in some places tomcat has it as a long, you are still running
> into this limitation so the problem is in the spec, and needs to be
> corrected there
I've seen this before in other containers, and honestly, I consider it a
bug.
Yes, the servlet specification defines Content-Length as an int.
However, you can see in the stack trace that Tomcat isn't using the
servlet API to fetch the Content-Length from the HTTP headers.
Instead, Tomcat could parse the header as a long integer and issue a
warning if the value is larger than Integer.MAX_VALUE.
This would still allow servlet code to fetch the Content-Length of a
request using request.getHeaderString("Content-Length") and parsing it
as a long integer.
Just my two cents.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGaqcE9CaO5/Lv0PARAk7TAJwJ+ZuGzoc1TnfhQT9deTEYF8G19QCePsix
cgM2luMToGtjfW8rygm16fI=
=hNAm
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
