-
Notifications
You must be signed in to change notification settings - Fork 38.9k
StandardServletMultipartResolver should support MaxUploadSizeExceededException against common servers [SPR-9294] #13932
Copy link
Copy link
Closed
Labels
in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)type: enhancementA general enhancementA general enhancement
Milestone
Description
Marten Deinum opened SPR-9294 and commented
Currently all exceptions thrown by the standard multipart support lead to the generic MultipartException. It would be nice if, like the CommonsMultipartResolver, there could be differentiated between a general exception or a MaxUploadSizeExceededException.
Probably not an easy task as it depends on the container how it is handled and which exception is thrown.
For tomcat it is:
org.apache.tomcat.util.http.fileupload.FileUploadBase$FileSizeLimitExceededException.
Affects: 3.1.1
Issue Links:
- CommonsMultipartFile.getOriginalFilename() should be able to preserve header-specified filename as-is [SPR-14613] #19180 CommonsMultipartFile.getOriginalFilename() should be able to preserve header-specified filename as-is
- CommonsMultipartResolver should explicitly convert FileSizeLimitExceededException next to SizeLimitExceededException [SPR-14638] #19204 CommonsMultipartResolver should explicitly convert FileSizeLimitExceededException next to SizeLimitExceededException
Referenced from: commits 1922f03
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)type: enhancementA general enhancementA general enhancement