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 a
I finally got out from under some work and was able to make some test
code. I'm attaching the client and servlet code.
The code transfers a couple parameters, then a binary file (I was using
a .jar). If you call the client with
"BinTestClient localhost something.jar b", it uses byte-by-byte rea
On Thu, 17 May 2001, Marc Saegesser wrote:
>
> 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.
>
3+ hours CVS update doesn't help either ( that's my current time on
xml-xalan, tomcat is slightly fas
>
> 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 proble
27;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 Uploa
Hi David,
How is your servlet handling the data in the byte array
being returned from Tomcat? Also, what corruption are
you seeing?
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 up
>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 f
: 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
masking off all but the lowest 8 bits and then turning the results back into
a byte looks like a no-op to me.
> -Original Message-
> From: DAK [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 16, 2001 10:59 PM
> To: [EMAIL PROTECTED]
> Subject: Servlet Upload Data Co
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 ServletInput
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 send
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 send
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 jar file to the servlet. The jar
file was getting corrupted. After much digging, I found a CVS commit to
Ajp13ConnectorRequest.java that mentioned a problem like th
13 matches
Mail list logo
