David,
A detailed bug report w/ test case is *great*, but it would also be very,
very helpful if you could specify:
1) What version of Tomcat you are running (precisely)
2) What web server you are running, and its version
3) Your OS
-Dan
DAK wrote:
I finally got out from under some work
i didn't see any comments in commit messages that mentioned the problem
you are speaking of. can you find that comment again and send it?
thanks.
DAK wrote:
Here's my first submission! It pertains to Tomcat-3.2.1 and looks to be
the same in 3.2.2.b4
I have some client code that sends a
i didn't see any comments in commit messages that mentioned the problem
you are speaking of. can you find that comment again and send it?
thanks.
DAK wrote:
Here's my first submission! It pertains to Tomcat-3.2.1 and looks to be
the same in 3.2.2.b4
I have some client code that sends a
This is the log message to which I'm referring. It put the (char) in the
return statement of doRead()
revision 1.5.2.4
date: 2001/01/30 04:17:53; author: danmil; state: Exp; lines: +4 -4
Fixed (yet another) bug with File Upload. Tomcat was returning signed data
to servlets (via
Take a look at http://jakarta.apache.org/site/getinvolved.html for
information about contributting to Jakarta projects. Specifically, use
the -u option for generating diffs and send the diffs as attachments instead
of inline.
Could you explain a little more what these diffs accomplish? My
: Servlet Upload Data Corruption
|
|
| i didn't see any comments in commit messages that mentioned the problem
| you are speaking of. can you find that comment again and send it?
| thanks.
|
| DAK wrote:
|
| Here's my first submission! It pertains to Tomcat-3.2.1 and looks to be
| the same in 3.2.2
Could you explain a little more what these diffs accomplish? My
understanding of the fix that went into revision 1.5.2.4 to
fix the file upload problem was that doRead() returns an 'int' and was
causing the byte 0xFF to be sign extended into the integer -1 which is the
EOF
return value for
. That's why I asked for a clarification. I
don't see how the proposed changes would actually alter the outcome.
-Original Message-
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 17, 2001 10:51 AM
To: [EMAIL PROTECTED]
Subject: RE: Servlet Upload Data Corruption
Could
Ajpv12 does not handle uploads well due to design, so
most of upload bug fixes were never backported from Ajpv13.
The moral is to use only Ajpv13 or higher for uploads.
i've been uploading all different kinds of files (via post data) with
ajp12 for a while, and haven't seen any problems.
On Thu, 17 May 2001, Marc Saegesser wrote:
rant
These 2+ hour email delivery times are getting to be a real pain. It's
almost impossible to have multi-party communication with such delays.
/rant
3+ hours CVS update doesn't help either ( that's my current time on
xml-xalan, tomcat is
10 matches
Mail list logo
