Chuck,
I understand what you're saying and it does seem strange that the
commons-fileupload jar lives under the manager webapp.
However, my understanding is that this jar is part of the Apache Tomcat
base installation and that it plays a part in the processing of all HTTP
requests.
There is a class in that jar called FileUploadBase, which actually
checks the Content-Length of the HTTP request (I think it parses the
HTTP request as well). In the erronous jar commons-fileupload-1.0.jar
(the one that comes as part of the base install) it checks for a content
length of -1 and returns the response code 411 if that length is -1. It
shouldn't do this because Chunked Transfer sets the Content-Length to -1
and it must support Chunked Transfer to be HTTP 1.1. compliant. The same
class in commons-fileupload-1.2.jar doesn't carry out this check and
should therefore not return 411 for Chunked Transfer.
Do you see what I am saying? This commons-fileupload jar is part of
Apache Tomcat and is used to parse every HTTP request. When I send in
HTTP POST with more than 2016 bytes then the mobile's stack Chunks it.
That request never makes it as far as my Servlet because Apache Tomcat
rejects it and I'm pretty sure that it's the class in the
commons-fileupload jar that rejects it with an error of 411. I was
surprised that this jar lived under a webapp (albeit a Tomact shipped
webapp), as opposed to being part of the shared lib paths such as
common/lib or server/lib but that's where it is in 5.5.20.
I just need to know how to update it properly.
Regards, Patrick.
Caldarale, Charles R wrote:
From: Patrick Mc Erlean [mailto:[EMAIL PROTECTED]
Subject: Re: How do I update the commons-fileupdate JAR from
1.0 to 1.2?
My understanding is that the manager webapp is part of the
Apache Tomcat installation. It's definitely not my app.
But is it actually the one you're using from the mobile device? What's
the URL the mobile is using to access the server? Unless it's referring
to Tomcat's manager app, changing any jar under server/webapps/manager
will not have an effect.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
