You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Udo Schnurpfeil (JIRA)" <de...@myfaces.apache.org> on 2013/10/22 20:16:47 UTC
[jira] [Reopened] (TOBAGO-1086) Filter xml header from facelets in
the response writer
[ https://issues.apache.org/jira/browse/TOBAGO-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Udo Schnurpfeil reopened TOBAGO-1086:
-------------------------------------
> Filter xml header from facelets in the response writer
> ------------------------------------------------------
>
> Key: TOBAGO-1086
> URL: https://issues.apache.org/jira/browse/TOBAGO-1086
> Project: MyFaces Tobago
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.5.10, 2.0.0-alpha-2
> Environment: JSF 1.2 and 2.0
> JSF 2.1 has resolved this problem
> Reporter: Udo Schnurpfeil
> Assignee: Udo Schnurpfeil
> Priority: Minor
> Fix For: 1.5.11, 2.0.0-alpha-3, 2.0.0
>
>
> Facelets writing out the xml header into the response writer
> See also http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-696
> The xml header declaration inside the HTML output sometimes makes problems with internet explorer.
> To avoid performance degression we should filter exacly to this string: <?xml version="1.0" encoding="UTF-8"?>
> So we have the possiblilty to declare the source code correctly as long as the application uses UTF-8.
--
This message was sent by Atlassian JIRA
(v6.1#6144)