commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard (JIRA)" <>
Subject [jira] [Commented] (FILEUPLOAD-197) ServletFileUpload isMultipartContent method does not support HTTP PUT
Date Thu, 03 Jan 2013 10:28:14 GMT


Richard commented on FILEUPLOAD-197:

I have also encountered this problem. Whilst the spec may not specifically apply to PUT I
believe that in a practical sense it would be expected that this api could use PUT to replace
resources that were created via POST. How else then should they be replaced? The crux of the
issue of that it's not really possible to get the correct content type or content length of
the resource being "put", as if it's not a multi part request then those attributes are those
of the request, not of the resource. To support this, multipart request has to be allowed
for PUT.
> ServletFileUpload isMultipartContent method does not support HTTP PUT
> ---------------------------------------------------------------------
>                 Key: FILEUPLOAD-197
>                 URL:
>             Project: Commons FileUpload
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>            Reporter: David Wolverton
> This method explicitly checks for method POST. I believe the PUT method can also have
multipart requests, and there may be others. In our case we are receiving rest calls using
Spring Framework's CommonsMultipartResolver which in turn uses this method of the Commons
FileUpload library.
> Here is the offending code...
> if (!"post".equals(request.getMethod().toLowerCase())) {
>     return false;
> }

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message