[ http://issues.apache.org/jira/browse/TOMAHAWK-208?page=comments#action_12421268 ] Siarhei Dudzin commented on TOMAHAWK-208: -----------------------------------------
The fix does not work because if the string is received from ServletRequest in already bad form. Applying correct encoding was a good idea but not enough... > inputSuggestAjax does not set content type of the response > ---------------------------------------------------------- > > Key: TOMAHAWK-208 > URL: http://issues.apache.org/jira/browse/TOMAHAWK-208 > Project: MyFaces Tomahawk > Issue Type: Bug > Components: InputSuggestAjax > Affects Versions: 1.1.2-SNAPSHOT > Environment: MyFaces (with Sandbox), Facelets > Reporter: Aleksei Valikov > Assigned To: Gerald Müllan > Priority: Minor > Fix For: 1.1.3 > > Attachments: ajaxCharacterEncodingFix.patch, > ajaxCharacterEncodingFix2.patch, ajaxDecodePhaseListener.patch > > > When inputSuggestAjax gets rendered, the AjaxDecodePhaseListener does not set > the content type of the response to the (expected) text/html;charset=UTF-8 > (or whatever). There's not type or charset specified at all. Below is the > trace of the typical inputSuggestAjax response: > HTTP/1.1 200 OK > Server: Apache-Coyote/1.1 > Content-Length: 6318 > Date: Tue, 21 Mar 2006 12:36:41 GMT > <table>...</table> > This results in natinal characters displayed incorrectly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
