https://bz.apache.org/bugzilla/show_bug.cgi?id=62664
Bug ID: 62664
Summary: @MultipartConfig, getParts(), and getParameter() on
PUT requests
Product: Tomcat 9
Version: 9.0.11
Hardware: Macintosh
Status: NEW
Severity: normal
Priority: P2
Component: Servlet
Assignee: dev@tomcat.apache.org
Reporter: schn...@gmail.com
Target Milestone: -----
Created attachment 36123
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36123&action=edit
HttpServlet subclass which will echo parameters for POST and for PUT before and
after calling getParts()
This is about a servlet annotated with @MultipartConfig.
For POST requests, "parts with form-data as the Content-Disposition but without
a filename" are available to getParameter*.
For PUT requests, such parts are not initially available to getParameter*. If
I call getParameter* before getParts(), they are never available to
getParameter*, even after calling getParts(). If I call getParts() first, then
they are available to getParameter*.
The servlet spec does not appear to require that PUT and POST should behave
differently for multipart requests in servlets annotated with @MultipartConfig.
Even if it did, it seems very surprising that the call order of getParts() vs
getParameter* would affect which parameters were available.
Tried on Tomcat 9.0.11 (and also some earlier versions), with Oracle Java 8.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
