[jira] Resolved: (WICKET-2514) Encoding issue with wicket Ajax POST form processing

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-2514.
-----------------------------------

    Fix Version/s: 1.5-M2
       Resolution: Fixed

ok, i will take your word for it. maybe im not seeing it because i am in en_us locale. fixing only in 1.5 because we do not want to change existing behavior

> Encoding issue with wicket Ajax POST form processing 
> -----------------------------------------------------
>
>                 Key: WICKET-2514
>                 URL: https://issues.apache.org/jira/browse/WICKET-2514
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.3.4
>         Environment: IE6, FF3
>            Reporter: Vincent MATHON
>            Assignee: Igor Vaynberg
>             Fix For: 1.5-M2
>
>
> Ajax submitted forms via POST are not encoded properly when wicket applications are configured for a charset different from UTF-8.
> (I mean for instance getMarkupSettings().setDefaultMarkupEncoding("ISO-8859-1"); getRequestCycleSettings().setResponseRequestEncoding("ISO-8859-1");)
> This bug is clearly related to old wicket mailing-list posts:
> http://mail-archives.apache.org/mod_mbox/wicket-users/200804.mbox/%3Cdf3d7452-0ac0-4cf7-8164-87e9371d82b1@signicat.com%3E
> http://www.nabble.com/BUG-on-wicket-ajax.js-on-Ajax-behaviour-in-IE7----to20915921.html#a20915921
> Changing t.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");  with t.setRequestHeader("Content-Type", "application/x-www-form-urlencoded;charset=UTF-8"); in wicket-ajax.js solves the problem without adding any specific web server configuration setting (like URIEncoding="UTF-8" for TOMCAT). This is the best solution if one not wants to sacrify web application portability. More, it seems that Ajax form processing should always be encoded in UTF-8 (see WicketFilter implementation switch in case of ajax request), so specifiying charset in the javascript should not be a problem.
> The javascript code for Ajax POST processing is identical in wicket 1.4.1 so this bug should also appear in this version.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.