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

Alexis Barrera commented on WW-4345:
------------------------------------

Our issue is similar but it happens even for files well below the file limit 
size. Before we patched the Dispatcher, we tried raising every limit (in 
struts, web.xml, and server.xml) to over 1GB and still had problems with a test 
file under 10KB.

I'll create a stub with archetype including all the libraries we use as well as 
the stacks we set up for upload.

> 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
>             Fix For: 2.3.18
>
>         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.2#6252)

Reply via email to