[ 
https://issues.apache.org/jira/browse/WICKET-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134067#comment-13134067
 ] 

Adam Pierzchała commented on WICKET-3525:
-----------------------------------------

In wicket 1.4.18 I have quite similar problem, whole file is being uploaded 
despite the fact that there is not enough space on disk. I used setMaxSize to 
set 10GB, but I have only 4GB. If I try to upload bigger file than 4GB, nothing 
happens after file is sent (Chrome reaches 100% upload, and then nothing 
happens, code doesn't reach my onSubmit, and debugging doesn't seem to help to 
understand what happens).

Can anybody tell me if this might be related or should I open new ticket for 
this?
                
> Fileupload: full request body is read even when it is known that it is larger 
> than the max allowed size
> -------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-3525
>                 URL: https://issues.apache.org/jira/browse/WICKET-3525
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.5-RC2
>            Reporter: Attila Király
>         Attachments: WICKET-3525-AJAX-handler.patch, WICKET-3525.patch
>
>
> Steps to reproduce (works with all major browers, I suggest using Chrome for 
> this because it shows the upload progress status with a percentage in the 
> lower left/right corner):
> 1. Go to http://www.wicket-library.com/wicket-examples/upload/single
> 2. Choose a file significantly larger than 100KB (app's max allowed size) for 
> the first form. Post the first form.
> 3. The post will take long because the file is uploaded and processed by the 
> server.
> The browsers send the content-length header and wicket compares this with the 
> max allowed upload size in 
> o.a.w.util.upload.FileUploadBase.FileItemIteratorImpl.FileItemIteratorImpl(FileUploadBase,
>  RequestContext). It detects that it is larger than allowed and throws an 
> exception which brakes the input parsing started by the Form component. 
> However the input is still processed by something else.

--
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


Reply via email to