[jira] [Commented] (MYFACES-3400) jsf.js: improvement of the encoding handling

["Werner Punz (Commented) (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/MYFACES-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152840#comment-13152840 ] 

Werner Punz commented on MYFACES-3400:
--------------------------------------

Here is a final result of my investigation.

a) Character encoding can easily be detected
b) We can change the request header accordingly
c) All browsers except firefox pick that up properly
d) The response then comes properly in the encoding given by the original page (response header is set properly)
e) The encoding of the response xml is marked properly in the encoding of the request in Mojarra, Mojarra behaves properly there. MyFaces has an issue there by always sending the response content type in the partial response writer in UTF-8.

So the question now is in which direction to go.
Firefox has a problem, but does this really affect us. Since we nailed down the encoding incorrectly
until now clientside to utf-8 and not to many users were affected, we probably can fix the issue without
giving to many problems for firefox users. The downside is we would break backwards compatibility.

If we make this behavior default off and add a config param one way or the other, we would be backwards
compatible but would introduce yet another parameter.

For myfaces alone we can live with the config param, but I am looking for a better solution here.

                
> jsf.js: improvement of the encoding handling
> --------------------------------------------
>
>                 Key: MYFACES-3400
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3400
>             Project: MyFaces Core
>          Issue Type: New Feature
>    Affects Versions: 2.0.10, 2.1.4
>            Reporter: Werner Punz
>            Assignee: Werner Punz
>
> Currently the default behavior for the encoding is UTF-8 for an ajax request with a config param for overriding the default encoding. Now due to a user request this does not work out. We need to have the ajax encoding more flexible. The idea is to detect the ajax encoding one way or the other (probably by dom parsing) and to adjust the request encoding accordingly.
> Investigation and code will be logged under this issue. However it is not sure if the final result will make it into 2.1, accordingly to the JSF-EG and the Mojarra people we will discuss it out whether the fixup will make it into the 2.1 codebase or not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira