commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (FILEUPLOAD-164) gracefully handle SizeLimitExceededException caused by exceeding fileSizeMax
Date Mon, 01 Sep 2008 07:03:44 GMT

     [ https://issues.apache.org/jira/browse/FILEUPLOAD-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Wiedmann resolved FILEUPLOAD-164.
----------------------------------------

    Resolution: Won't Fix
      Assignee: Jochen Wiedmann

I think there is no need for an API extension or any code changes. IMO, you already have everything
that is required to resolve your issue elegantly:

- Use the streaming API (most likely recommended in your case anyways).
- Do *not* set the file item size limitations. (OTOH, you might consider to limit
  the requests size to something like max size of 30 items.)
- For any item: Get the items input stream. Replace it with an instance of
  LimitedInputStream. Read and process the item, while catching the
  exception. If the exception pops up, simply ignore the item and proceed
  to the next.


> gracefully handle SizeLimitExceededException caused by exceeding fileSizeMax
> ----------------------------------------------------------------------------
>
>                 Key: FILEUPLOAD-164
>                 URL: https://issues.apache.org/jira/browse/FILEUPLOAD-164
>             Project: Commons FileUpload
>          Issue Type: Wish
>    Affects Versions: 1.2.1
>            Reporter: Olaf Freyer
>            Assignee: Jochen Wiedmann
>
> I have a feature/improvement request:
> when uploading X files of which Y files exceed fileSizeMax I'd love to be able to handle
the X-Y remaining files that didn't break the constraint.

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


Mime
View raw message