Operation failed due to error c00ce56e

Question

I upgraded from rich 3.3 to rich 4.2 because ajax did not work for IE9. Now it still does not work.

After receiving the response, IE receives error JS "SCRIPT58734: Der Vorgang konnte aufgrund des folgenden Fehlers nicht fortgesetzt werden: c00ce56e." upon attempt

data.responseText=request.responseText 

on jsf.js.html? ln = javax.faces & conversationContext = 2, line 1 line 21747

I think this is due to the HTTP increcct header

 Content-Type: text/xml;charset=UTF8 

it should be

 Content-Type: text/xml;charset=UTF-8 

Here's the raw server response

 HTTP/1.1 200 OK Server: Apache-Coyote/1.1 X-Powered-By: JSF/2.0 Cache-Control: no-cache Content-Type: text/xml;charset=UTF8 Content-Length: 293 Date: Tue, 17 Apr 2012 15:25:22 GMT <?xml version='1.0' encoding='UTF8'?> <partial-response><changes><update id="outtest"><![CDATA[<span id="outtest"><span class="outhello">Hello !</span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[2809980525147413088:295565165947012503]]></update></changes></partial-response> 

I use

 javaee-web-api 6 myfaces-orchestra-core 1.4 Hibernate 4.1 Spring 3.1.1 Richfaces 4.2.0 Primefaces 3.2 jsf-api+impl 2.1.7 

jstl 1.2

and works on tomcat 7

EDIT: now i'm sure this is the title. I set a breakpoint in charles-proxy and edited the response header manually, and the edited IE9 HTTP header showed the correct result without errors

Answer 1

Your analysis is correct. The charset attribute in the Content-Type header is c00ce56e , and IE9 pinches this with error c00ce56e .

JSF uses the default one that is obtained from ServletRequest#getCharacterEncoding() . Usually this parameter defaults to the one specified by the client or null if it is absent (which often happens). This is usually overridden with some custom filter that calls request.setCharacterEncoding() .

Given the wrong encoding, this could mean that your web application is calling request.setCharacterEncoding() somewhere with "UTF8" instead of "UTF-8" . "UTF-8"

I would start checking all the filters and their configuration.