A number of problems resulting from the use of the text/html MIME type in conjunction with XHTML content are discussed. It is suggested that XHTML delivered as text/html is broken and XHTML delivered as text/xml is risky, so authors intending their work for public consumption should stick to HTML 4.01, and authors who wish to use XHTML should deliver their markup as application/xhtml+xml.
Sorry, if that's widely known. I just found pretty interesting.Context
This was originally written in September 2002 in the context of this Web log entry:
It has since been regularly updated to correct errors that have been brought up in various mailing lists and other discussion forums. As of late 2004, it is still just as relevant as when it was originally written.
Note that this document compares XHTML 1.0 compliant to appendix C to HTML 4.01, because that is the only variant of XHTML that may be sent as text/html.
EDIT: I forgot to post a little question I had in mind?
Having read that article, it looks like IE6 (and of course other legacy browsers) doesn't support XHTML Strict. Does that mean it is required to somehow "detect" the browser prior to sending the headers (mimetype application/xhtml+xml and the xhtml doctype)?