[
https://issues.apache.org/jira/browse/FILEUPLOAD-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595136#comment-13595136
]
Roy T. Fielding commented on FILEUPLOAD-197:
--------------------------------------------
PUT means the sent representation is the replacement value for the target
resource. A server could certainly support that functionality using any
container format, it wouldn't be "normal" to use a MIME multipart, nor is it
expected to be supported by the file upload functionality defined for browsers
in RFC1867.
If you want to PUT a package, I suggest defining a resource that can be
represented by an efficient packaging format (like ZIP) and then using PUT on
that resource to have the side-effect of updating the values of its subsidiary
resources.
> ServletFileUpload isMultipartContent method does not support HTTP PUT
> ---------------------------------------------------------------------
>
> Key: FILEUPLOAD-197
> URL: https://issues.apache.org/jira/browse/FILEUPLOAD-197
> Project: Commons FileUpload
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: David Wolverton
> Fix For: 1.3
>
>
> 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: http://www.atlassian.com/software/jira