The specification for xhtml-1.1 says that the server *should* send application\/xml+xhtml in the HTTP header but that it *can* send text\/html in order to remain backwards compatible with older user agents, IE for example. As long as the doctype is set correctly (and it is) it is still valid xhtml-1.1.<\/p>\n
In fact, if you use the validator<\/a> and let it auto detect the doctype it correctly detects xhtml-1.1 and validates the page using that specification (ignore the errors, I’m still workin’ on it). Browsers will also detect it, including IE, and use the correct specs to render the page. They also render the page in Standards Compliance Mode, including IE.<\/p>\n Trust me on this, I researched it *extensively* before making the jump to xhtml-1.1, I didn’t just blindly decide to change. I read the entire xhmtl-1.1 specification. I didn’t just skim it or skip any parts I read the entire thing. I read the XSLT-1.0 specification to make sure I was doing it right in the xsl. I also read TONS of threads from all over the world discussing this, including from IE support sites, apache, mozilla, w3c and web designer sites. <\/p>\n MS officially suggests using text\/html in the HTTP header when serving xhtml-1.1 documents to IE. Mozilla, Opera, Firefox, Konqueror can all correctly use application\/xml+xhtml and officially suggest that is what you send in the HTTP header but **ALL** of them are also backwards compatible with text\/html.<\/p>\n None of the text browsers, as far as I know, can use application\/xml+xhtml yet but, just like IE, they can correctly render an xhtml-1.1 page validly and in Standards Compliance Mode with text\/html in the HTTP header.<\/p>\n So, to sum it up:<\/p>\n The site is validly serving XHTML-1.1 (except for the errors I haven’t fixed yet) that is recognized by all browsers and correctly rendered. The server doesn’t have to send application\/xml+xhtml in the HTTP header in order for it to be valid, it can send text\/html too.<\/p>\n","protected":false},"excerpt":{"rendered":" The specification for xhtml-1.1 says that the server *should* send application\/xml+xhtml in the HTTP header but that it *can* send text\/html in order to remain backwards compatible with older user agents, IE for example. As long as the doctype is set correctly (and it is) it is still valid xhtml-1.1. In fact, if you use … Continue reading xhtml-1.1<\/span><\/a><\/p>\n","protected":false},"author":26,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/posts\/13"}],"collection":[{"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/comments?post=13"}],"version-history":[{"count":1,"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/posts\/13\/revisions"}],"predecessor-version":[{"id":31,"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/posts\/13\/revisions\/31"}],"wp:attachment":[{"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/media?parent=13"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/categories?post=13"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.gentoo.org\/curtis119\/wp-json\/wp\/v2\/tags?post=13"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}