[jira] Commented: (FILEUPLOAD-144) Parameters values are lost

["Kazuhito Ishigaki (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FILEUPLOAD-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531400 ] 

Kazuhito Ishigaki commented on FILEUPLOAD-144:
----------------------------------------------

I got same problem last week on Tomcat in public service.

It happens NOT only slow input stream.
I reproduced it on my local network.
I watched the size of read bytes, It was 37 or 39 sometimes.
It is enough to happen the Bug (because IE uses 40byte for boundary).
The reason why it happens, I think the LimitedInputStream.
There is no bug in the class, but it makes fragment.


> Parameters values are lost
> --------------------------
>
>                 Key: FILEUPLOAD-144
>                 URL: https://issues.apache.org/jira/browse/FILEUPLOAD-144
>             Project: Commons FileUpload
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: JBoss 4 / XP / Servlet / both Firefox and IE
>            Reporter: Vera Mickael
>            Priority: Critical
>         Attachments: correction_with_test_cases_in_distribution.zip, MultipartStream.java, test.fileupload.zip, test.fileupload.zip
>
>
> When parsing a request with the streaming API, some parameters loose their values. I can easily reproduce the problem when a lot of parameters are submitted (about 400 in a table). My code is as follows :
>             final FileItemStream itemStream = anItemIterator.next();
>             final String fieldName = itemStream.getFieldName();
>             System.out.print("Field " + fieldName);
>             InputStream stream = itemStream.openStream();
>             final String value = Streams.asString(stream, "UTF-8");
> The last statement sometimes returns a value and sometimes not. Sometimes I can retreive all parameters, sometimes I loose 3 or 4 parameters. I reproduced the problem on two computers. I have a very small application with a servlet of 69 lines that reproduces the problem, the project is attached to this issue. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.