Re: [xml] Bug in encoding detection with document()

Bjoern Hoehrmann wrote:
* Chuck Bearden wrote:
It appears that libxslt1.1 pays attention to the charset declaration in the Content-Type HTTP header when retrieving XML files with MIME types of application/xml or text/xml via the document() function. If a misconfigured web server sends "Content-Type: text/xml; charset=iso-8859-15" but the XML file itself has no encoding declaration in the XML prolog (and is thus to be taken as UTF-8), libxslt treats the incoming file as ISO-8859-15 and so mangles byte sequences that express e.g. many common vowels with diacritics.

The charset parameter takes precedence over internal labels and defaults
so it is the misconfigured server that mangles those sequences. See e.g.
RFC 3023 for a discussion.

Thanks for the information. So it looks like in this case Saxon 6.5.5 is not following the RFC.

When you say that the misconfigured server mangles the bytes, I take it that you mean it does so by virtue of giving the wrong information to libxslt. The test files are byte-for-byte identical when retrieved with wget, so they aren't directly modified by the server.

Thanks again for the info.  I appreciate the pointers.
Chuck Bearden (cbearden rice edu ; 713.348.3661)
XML Engineer, Connexions

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]