As far as I know, no User Agent (besides the W3C validator) repects the content-type header.  It's a bit of a pain.

Sans headers (like if your opening a local file) Firefox (and I'm gruessing the whole Gecko family) will treat a file as application/xhtml+xml if the extention is .xhtml, if it's .xml it will call it text/xml, but the rendering effect will be the same.

With websites it's a bit tricky.  The problem is that some of the legacy browsers (at least IE) go all funny when you send them application/xml+xtml. Ideally you can use something like PHP and check the
"HTTP_ACCEPT" header like this.  Otherwise IE tries to save your pages instead of view them.

Alan Trick

Townson, Chris wrote:
In both Mozilla and Opera, I found that what was crucial was that the server (Apache, in this instance) was configured to deliver the file as application/xhtml+xml (+ being well formed, of course). Merely setting this in the document head was not sufficient. Thus, tidying up the code and adding "AddType application/xhtml+xml .xhtml" to httpd.conf got everything running smoothly.

Reply via email to