You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mat Gessel (Commented) (JIRA)" <ji...@apache.org> on 2012/01/17 01:07:39 UTC
[jira] [Commented] (FILEUPLOAD-135) InputStream created with
Streaming API returns EOF on first read() for short files uploaded from
FireFox over HTTPS
[ https://issues.apache.org/jira/browse/FILEUPLOAD-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187325#comment-13187325 ]
Mat Gessel commented on FILEUPLOAD-135:
---------------------------------------
Incidentally, I started triggering this bug after updating to JRE 1.7 u1 on the *client*. I have a standalone Java application that is uploading files to a Tomcat container via HTTPS/SSL.
Reproduction requires:
- HTTPS/SSL transmission
- jdk1.7.0_u1 or later
- commons-fileupload-1.2.0 or previous
Fixed with commons-fileupload-1.2.1 or later
> InputStream created with Streaming API returns EOF on first read() for short files uploaded from FireFox over HTTPS
> -------------------------------------------------------------------------------------------------------------------
>
> Key: FILEUPLOAD-135
> URL: https://issues.apache.org/jira/browse/FILEUPLOAD-135
> Project: Commons FileUpload
> Issue Type: Bug
> Affects Versions: 1.2, 1.2.1
> Environment: Windows XP
> Browser: Firefox 1.5.0.11
> Protocol: HTTPS
> Reporter: Alexander Sova
> Assignee: Jochen Wiedmann
> Fix For: 1.2.1
>
> Attachments: FILEUPLOAD135.patch, commons-fileupload-1.1-bug-short-file-eof.patch, commons-fileupload-1.2-bug-short-file-eof.patch
>
>
> This problem happens only with files shorer then boundary string generated by browser and only with Firefox using HTTPS protocol.
> For some reason in this particular environment inputStream.read() in MultipartStream.ItemInputStream.makeAvailable() reads not whole HTTP response body, but only file content before boundary string.
> I've created a patch fixing this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira