> Collin Davis > Per the W3C > specs, XHTML should be served as application/xhtml+xml or > application/xml or > text/xml and should not be served as text/html.
Actually, it doesn't say "should not"! As per section 5.1, it actually states that documents "may" be sent as text/html: "XHTML Documents which follow the guidelines set forth in Appendix C, "HTML Compatibility Guidelines" may be labeled with the Internet Media Type "text/html" [RFC2854], as they are compatible with most HTML browsers. " http://www.w3.org/TR/xhtml1/#media > I've never really understood this > - it's very > easy to use content negotiation to serve up HTML 4.01 as text/html to > browsers that can't handle the proper MIME type, and XHTML 1.0/1.1 as > application/xhtml+xml to those that can. So your server actually sends clean HTML 4.01 to those browsers that can't handle XHTML? Does it strip out the self-closing slashes? Or are you sending XHTML with a text/html mime type (which you previously said "should not" be done)? Patrick ________________________________ Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.uk ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
