jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1621) Use application/xml as the XML media type
Date Thu, 22 May 2008 12:57:55 GMT

    [ https://issues.apache.org/jira/browse/JCR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599005#action_12599005
] 

Jukka Zitting commented on JCR-1621:
------------------------------------

Following up from JCR-1310, in revision 659095 I made sure that the exported XML is always
encoded in UTF-8 and that the Content-Type header is set to "text/xml; charset=UTF-8" which
should be safe.

I'll review the other cases listed by Angela to see what (if anything) we should do.

> Use application/xml as the XML media type
> -----------------------------------------
>
>                 Key: JCR-1621
>                 URL: https://issues.apache.org/jira/browse/JCR-1621
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-webdav
>            Reporter: Jukka Zitting
>            Priority: Minor
>
> As noted in JCR-1310, at least in jackrabbit-webapp but possibly also elsewhere we should
be using application/xml instead of text/xml as the content type when serving XML over HTTP.
> The text/xml type has been widely criticized because of character encoding issues (see
for example http://www.xml.com/pub/a/2004/07/21/dive.html), and there has even been an attempt
to officially deprecate text/xml because of this. The application/xml type doesn't suffer
from these issues, and is thus a better choice when serving XML.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message