I have been following this discussion (belatedly)
It's all in the MIME http://www.juicystudio.com/all-in-the-mime.asp
first paragraph: " There have been a lot of articles recently about web standards; in particular, using XHTML and serving it as text/html. Personally, I'm not that bothered whether people serve XHTML as text/html, but think it's important that authors understand why this is wrong. Although I'm not bothered about content developers serving XHTML as text/html, I don't agree with people encouraging content developers to deliver XHTML as text/html. "
I wondered what other memebrs on the list thought about it and its implications?
Others have written about it and about server-side solutions to cater for IE while still sending application/xhtml+xml to the likes of Mozilla, Opera and the W3 HTML validator:
1 - The issue [http://www.hixie.ch/advocacy/xhtml]
2 - The parsing consequences (old, but still valid): [http://www.hut.fi/~hsivonen/test/xhtml-suite/xhtml-index]
3 - The solution (PHP) [http://www.workingwith.me.uk/articles/scripting/mimetypes/]
4 - The solution (.htaccess, can't recall the source):
RewriteEngine On
RewriteCond %{HTTP_ACCEPT} application/xhtml\+xml
RewriteCond %{HTTP_ACCEPT} !application/xhtml\+xml\s*;\s*q=0
RewriteCond %{REQUEST_URI} \.html$
RewriteCond %{THE_REQUEST} HTTP/1\.1
RewriteRule .* - [T=application/xhtml+xml]
Ciao,
Jeroen
-- vizi fotografie & grafisch ontwerp - http://www.vizi.nl/
****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
