Wednesday, June 8, 2011

application/xml vs text/xml

Just reblogging this precious information:

"XML has two MIME types, application/xml and text/xml. These are often used interchangeably, but there is a subtle difference which is why application/xml is generally recommended over the latter.

Let me explain why: according to the standard, text/*-MIME types have a us-ascii character set unless otherwise specified in the HTTP headers. This effectively means that any encoding defined in the XML prolog (e.g. ) is ignored. This is of course not the expected and desired behaviour.

To further complicate matters, most/all browser implementations actually implement nonstandard behaviour for text/xml because they process the encoding as if it were application/xml.

So, text/* has encoding issues, and is not implemented by browsers in a standards-compliant manner, which is why using application/* is recommended.


That's yet another of those things which make SOAP so exciting: a poor standard poorly implemented poorly defined and poorly respected. It must be on purpose, I can't believe engineers are so stupid.

No comments: