Hide Forgot
Date of First Response: 2009-11-16 11:35:46 project_key: SOA The admin-console's ( http://localhost:8080/admin-console ) HTTP response contains following headers: Server: Apache-Coyote/1.1 X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1, JSF/1.2 Content-Type: text/html; charset=UTF-8;charset=UTF-8 Transfer-Encoding: chunked Date: Mon, 16 Nov 2009 14:57:52 GMT 200 OK Notice the invalid (doubled) charset value of Content-Type header. With this header it can cause following exception: "java.nio.charset.IllegalCharsetNameException: UTF-8;charset=UTF-8"
This is an issue with EAP 5.0 GA (or Seam). To repeat: Install lynx. Start up EAP 5.0.0 GA. Run: lynx -trace http://localhost:8080/admin-console/ Press 'y' to accept the cookie. Press <return> to load http://localhost:8080/admin-console/index.seam In another terminal run: grep Content-Type $HOME/Lynx.trace Notice the line containing "text/html;charset=utf-8;charset=utf-8"
A work around appears to be editing the following files: .../server/<profile>/deploy/admin-console.war/index.xhtml .../server/<profile>/deploy/admin-console.war/WEB-INF/facelets/layout.xhtml .../server/<profile>/deploy/admin-console.war/WEB-INF/facelets/errorLayout.xhtml .../server/<profile>/deploy/admin-console.war/login.xhtml and changing the lines: <f:view contentType="text/html; charset=UTF-8"> to: <f:view contentType="text/html"> because "charset=utf-8" is being appended to the contentType line.
The Seam guide, chapter 16, "Internationalization, localization and themes": http://docs.jboss.org/seam/2.1.2/reference/en-US/html/i18n.html contains more information on setting the character encoding.
Note, that RFC2045, section 5 "Content-Type Header Field" does not state that parameters should not be duplicated. So, it looks like a bug in the HTML parser to reject the duplicated charset attribute and treat it as a single value of "UTF-8;charset=UTF-8".
Fixed in revision 4169 of: build-tools/builders/eap/post-patch/patch_admin_console_ui.xml Commit message: SOA-1603 Workaround for duplicated charset that confuses some clients.
Link: Added: This issue is related to JBPAPP-3132
Verified in ER4