You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/16 09:38:34 UTC

[jira] [Commented] (WW-4345) Struts Dispatcher gobbles up request parameters

    [ https://issues.apache.org/jira/browse/WW-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135097#comment-14135097 ] 

ASF subversion and git services commented on WW-4345:
-----------------------------------------------------

Commit 63fa04e8146ec02fc256fa35a93454482254dcef in struts's branch refs/heads/develop from [~lukaszlenart]
[ https://git-wip-us.apache.org/repos/asf?p=struts.git;h=63fa04e ]

WW-4345 Reverts the commit 8aa4fe860693d29e5ef94026bf2a7532ed74b9ea


> Struts Dispatcher gobbles up request parameters
> -----------------------------------------------
>
>                 Key: WW-4345
>                 URL: https://issues.apache.org/jira/browse/WW-4345
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Dispatch Filter
>    Affects Versions: 2.3.16.3
>            Reporter: Alexis Barrera
>            Assignee: Lukasz Lenart
>             Fix For: 2.3.x
>
>         Attachments: mulipart-patch.diff
>
>
> Unfortunately, I'm passing this ticket on to you second-hand so please bear with me.
> Since at least version 2.3.3 we have had a problem with Struts and multipart/form uploads. The problem is intermittent and we'd had a really hard time getting it to occur consistently on all our servers, but it seems to happen pretty reliably on Red Hat.
> The problem is basically this: When a multipart upload is received by Struts, the action responsible for the request is instantiated without any information about the upload. We expect to get the file name/type/content as per: http://struts.apache.org/release/2.3.x/docs/file-upload.html but get null values instead.
> We were able to track the problem back into the org.apache.struts2.dispatcher.Dispatcher a while back and circumvented the issue as you can see in the attached patch ... but we don't know enough about Struts to figure out if a fix should be applied elsewhere.
> It's entirely possible we're using Struts wrong, but we tried pretty hard to find the right upload configuration and couldn't get reliable results until we patched.
> Please let me know if need more information to reproduce the problem. Our CMS is behind a firewall, so I can't point you to a live page but would be glad to give you more details about the JARs we use and how we have Struts configured.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)