[
https://issues.apache.org/jira/browse/WW-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516276#comment-17516276
]
Sergey Zolotarev commented on WW-5176:
--------------------------------------
That's a good advice, but it's not a solution though I think. The framework is
supposed to handle all valid multipart requests by default. Not to mention that
it's a breaking change, because an earlier version of Struts processed the same
request without any problem.
> multipart/form-data parameters are not processed when charset is placed
> before boundary in Content-Type header
> --------------------------------------------------------------------------------------------------------------
>
> Key: WW-5176
> URL: https://issues.apache.org/jira/browse/WW-5176
> Project: Struts 2
> Issue Type: Bug
> Components: Dispatch Filter
> Affects Versions: 2.5.29
> Reporter: Sergey Zolotarev
> Priority: Major
>
> The regex used inside isMultipartRequest() in Dispatcher.java expects the
> charset directive to be in the middle between the media type and boundary,
> but there are third-party libraries that append it after "bounary", which
> seems legitimate to me.
> i.e. this works:
> {code:java}
> Content-Type: multipart/form-data; bounary=123467890; charset=utf-8{code}
> this doesn't work:
> {code:java}
> Content-Type: multipart/form-data; charset=utf-8; bounary=123467890{code}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
