Return-Path: X-Original-To: apmail-struts-issues-archive@minotaur.apache.org Delivered-To: apmail-struts-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9504811327 for ; Tue, 13 May 2014 05:33:36 +0000 (UTC) Received: (qmail 83988 invoked by uid 500); 13 May 2014 05:26:15 -0000 Delivered-To: apmail-struts-issues-archive@struts.apache.org Received: (qmail 83851 invoked by uid 500); 13 May 2014 05:26:15 -0000 Mailing-List: contact issues-help@struts.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@struts.apache.org Delivered-To: mailing list issues@struts.apache.org Received: (qmail 83709 invoked by uid 99); 13 May 2014 05:26:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 May 2014 05:26:15 +0000 Date: Tue, 13 May 2014 05:26:15 +0000 (UTC) From: "Lukasz Lenart (JIRA)" To: issues@struts.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (WW-4345) Struts Dispatcher gobbles up request parameters MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/WW-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996061#comment-13996061 ] Lukasz Lenart commented on WW-4345: ----------------------------------- What's the problem here? I can figure it out based on the patch but I'm not sure if this the right solution as no one else reported such a problem. Can you share your setup or prepare a small demo app Maven based? > 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)