struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Don Brown (JIRA)" <>
Subject [jira] Closed: (STR-103) Token control does not work for a form of enctype="multipart/form-data"
Date Tue, 25 Apr 2006 19:15:45 GMT
     [ ]
Don Brown closed STR-103:

    Resolution: Fixed

> Token control does not work for a form of enctype="multipart/form-data"
> -----------------------------------------------------------------------
>          Key: STR-103
>          URL:
>      Project: Struts Action 1
>         Type: Improvement

>   Components: Action
>     Versions: Nightly Build
>  Environment: Operating System: All
> Platform: PC
>     Reporter: strutsbugs
>     Assignee: Craig McClanahan
>     Priority: Minor
>      Fix For: 1.0.0

> Using the same pattern as EditSubscriptionAction - SaveSubscriptionAction
> to set and check the token. Token control fails.  This should be atleast
> documented that in 1.0 as not working.
> There needs to be a way to shuttle the token over the multiple requests.
> This was originally posted by Richard Reich
> <> to the struts list.
> Name/value pairs that end up in the request parameter map stay
> deeply buried within a multi-part element data structure.  It is hard to
> call this obnoxious design problem in HTML/HTTP a Struts bug, in my opinion,
> although it does produce behavior within Struts applications that certainly
> looks and feels like bugs.
> It would be possible to "promote", on a case-by-case basis, the magic
> name/value pairs to the request parameter map.  The "populate" method in the
> RequestUtils class seems to be the appropriate choke-point.
> What do you recommend I do?  I am slightly reluctant to submit this problem
> (and my proposed solution, which might be totally wrong -- I still do not
> claim to understand the Struts upload package) as a bug, per se, but it is
> something that I believe must be incorporated in Struts at some point.
> Processing multipart form data is complicated and very bug prone (mysterious
> bugs too!) without it.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message