[
https://issues.apache.org/jira/browse/FILEUPLOAD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved FILEUPLOAD-140.
----------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 1.2.1)
Assignee: Jochen Wiedmann
You are free to use the streaming API, in which case you obviously receive the
items, which are read so far.
Continuing to read after a limit is exceeded, seems counterproductive, because
typically users will see such an exception as early as possible. This also
means, that your desire will fail completely, if the exception is raised due to
a content-length header. Apart from that, I do believe that this sounds like an
invitation for DOS attacks.
> Means to preserve text parameters when upload limit exceeded
> ------------------------------------------------------------
>
> Key: FILEUPLOAD-140
> URL: https://issues.apache.org/jira/browse/FILEUPLOAD-140
> Project: Commons FileUpload
> Issue Type: Improvement
> Affects Versions: 1.2
> Reporter: Paul Benedict
> Assignee: Jochen Wiedmann
>
> I am trying to resolve https://issues.apache.org/struts/browse/STR-2585 but
> am lacking the means to do it. The current use is with the deprecated
> DiskFileUpload and I prefer to have this class fixed first. When
> SizeLimitExceededException is thrown, it does not return the items it has
> collected thus far. I see two possible solutions which involve adding a
> property on the exception to return them:
> (1) Return the parameters thus gathered or
> (2) finish out the input stream but throw away all file items and return only
> the text parameters.
> Otherwise, whenever a the upload exceeds its limit, all other input
> parameters disappear.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
