[
https://issues.apache.org/jira/browse/FILEUPLOAD-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065509#comment-13065509
]
Jochen Wiedmann commented on FILEUPLOAD-197:
--------------------------------------------
I have never heard of something like that and I'd clearly read section 9.6 in
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html different:
The PUT method requests that the enclosed entity be stored under the
supplied Request-URI.
*The* enclosed entity. Not a multipart request with various entities.
Unless you can supply a a clear and convincing citation that shows me I am
wrong I intend to close this isue as INVALID.
> 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.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
