commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olaf Freyer (JIRA)" <>
Subject [jira] Commented: (FILEUPLOAD-164) gracefully handle SizeLimitExceededException caused by exceeding fileSizeMax
Date Thu, 28 Aug 2008 06:57:44 GMT


Olaf Freyer commented on FILEUPLOAD-164:

I'm writing a grails app that enables a user to upload media files.
It uses commons-fileupload via a spring CommonsMultipartResolver.

Basically a user can upload X files at once with a per-file size limit of N bytes.
As those files tend to be quite large it would be convenient for a user 
that even though some files might have violated the constraint ,
the remaining files should be processed and make it into the system.

Here is an example:
The user wants to upload 4 files with the given sizes: 97MB, 93MB, 110MB, 150MB.
Given a per file size constraint of 120MB what currently happens is that the user 
uploads about 420MB before the constraint is violated and an exception is thrown.
All uploading progress made so far is lost and all we can do is tell the user that 
some file violated the size constraint.
The way I'd prefer things to work is that even though the last file violates the constraint
the 3 files obeying the constraint (with a total size of 300MB) should be processed 
by the system.

> gracefully handle SizeLimitExceededException caused by exceeding fileSizeMax
> ----------------------------------------------------------------------------
>                 Key: FILEUPLOAD-164
>                 URL:
>             Project: Commons FileUpload
>          Issue Type: Wish
>    Affects Versions: 1.2.1
>            Reporter: Olaf Freyer
> 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.

View raw message