[WICKET-3525] Fileupload: full request body is read even when it is known that it is larger than the max allowed size

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.5-RC2
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Attila Király
• Created: 11/Mar/11 19:40
• Updated: 25/Apr/12 14:13

Description

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.

Issue Links

• is duplicated by: WICKET-3923 FileUploadField fails when upload size exceeds setMaxSize()
• is duplicated by: WICKET-4515 Upload Info used by Upload Progress Bar is missing error condition information