[
https://issues.jboss.org/browse/WFLY-3391?page=com.atlassian.jira.plugin....
]
Stuart Douglas commented on WFLY-3391:
--------------------------------------
Not really. You can't really default the configuration because there is no sensible
default that will work all apps.
Also I am not talking about a context param, but a <multipart-config> element that
is applied to the default servlet.
Multipart handling broken when HttpServletRequest accessed by servlet
filter
----------------------------------------------------------------------------
Key: WFLY-3391
URL:
https://issues.jboss.org/browse/WFLY-3391
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Undertow)
Reporter: Lincoln Baxter III
Assignee: Stuart Douglas
See forum post for full description:
http://ocpsoft.org/support/topic/command-not-fired-with-multipart-form-js...
I don't exactly know if this is a bug or not, but I wanted to raise the issue just in
case. It seems like a "corner" case that could occur quite easily, and given
that it requires a pretty nasty workaround (using undertow internals,) I figured it should
probably be addressed.
Should DefaultServlet be aware of multipart requests?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)