[
https://issues.apache.org/jira/browse/TAPESTRY-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506686
]
Jesse Kuhnert commented on TAPESTRY-1591:
-----------------------------------------
I've looked in to this and am not sure it's what you expect. By default right
now this parameter gets passed in to the dojo IO functions which use the native
browser encodeURIComponent for utf encoding of client side data and some manual
string process for any others.
Are you sure the problem is the request data going back to the server or is it
the response coming from the server? Is there some sample text I can use to
see this myself?
> Encoding for Ajax Request is always UTF-8
> -----------------------------------------
>
> Key: TAPESTRY-1591
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1591
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 4.1.2
> Reporter: Lionel Touati
>
> Ajax request encoding should match template content type.
> It should follow:
> org.apache.tapestry.output-encoding
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]