[
https://issues.apache.org/jira/browse/TAP5-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-1118.
--------------------------------------
Fix Version/s: 5.2.1
Resolution: Fixed
> Using Ajax updates to add an Upload component to an existing Form fails in
> IE, which still sends application/x-www-form-urlencoded encoded request
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1118
> URL: https://issues.apache.org/jira/browse/TAP5-1118
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-upload
> Affects Versions: 5.1.0.5
> Reporter: Raul Montes
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.1
>
>
> When injecting an upload component via form injector, it tries to set the
> enctype of the form to "multipart/form-data". This works ok on most browsers,
> but as expected, IE doesn't like it... IE still sends the POST request as
> "application/x-www-form-urlencoded".
> Nevertheless, there is a workaround
> (http://www.bennadel.com/blog/1273-Setting-Form-EncType-Dynamically-To-Multipart-Form-Data-In-IE-Internet-Explorer-.htm)
> that is to set not only the enctype but also the encoding of the form, which
> IE uses when submiting the form.
> In practice, it only requires to change upload.js to something like this:
> Tapestry.Initializer.injectedUpload = function(element)
> {
> var form = $(element).form;
> form.enctype = "multipart/form-data";
> form.encoding = "multipart/form-data";
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
