NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 431 - XHTML5 with text/xml mime type not allowed
XHTML5 with text/xml mime type not allowed
Status: RESOLVED INTENTIONAL
Product: Validator.nu
Classification: Unclassified
Component: General
HEAD
All All
: P2 normal
Assigned To: Henri Sivonen
http://www.mozillaquestquest.com/about
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-05 15:57 CET by Dean Edridge
Modified: 2009-01-06 01:55 CET (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dean Edridge 2009-01-05 15:57:39 CET
XHTML web pages served as text/xml are being validated as XHTML5 even though text/xml is not a valid XHTML5 mime type.

http://validator.nu/?doc=http%3A%2F%2Fwww.mozillaquestquest.com%2Fabout

I'm not sure what should happen here. Should we say that it is simply invalid, or say: "It seems you are trying to use XHTML5, you will need to use either the application/xhtml+xml or application/xml mime types as text/xml is not allowed for XHTML5.". Or something like: "Invalid mime type for XHTML5, use application/xhtml+xml or application/xml". Keep in mind of course, that officially, only pages served as application/xhtml+xml or application/xml are XHTML5.
Comment 1 Henri Sivonen 2009-01-05 18:04:34 CET
The spec says: “XHTML documents (XML documents using elements from the HTML namespace) that use the new features described in this specification and that are served over the wire (e.g. by HTTP) must be sent using an XML MIME type such as application/xml  or application/xhtml+xml and must not be served as text/html. [RFC3023]â€

Not “such asâ€. The list is not exhaustive. The reference is to RFC 3023, which also defines text/xml as an XML content type.
Comment 2 Dean Edridge 2009-01-06 01:55:38 CET
(In reply to comment #1)
> The spec says: “XHTML documents (XML documents using elements from the HTML
> namespace) that use the new features described in this specification and that
> are served over the wire (e.g. by HTTP) must be sent using an XML MIME type
> such as application/xml  or application/xhtml+xml and must not be served as
> text/html. [RFC3023]â€

Yeah, I know what the spec says, but it appears I've misread it.
 
> ... which also defines text/xml as an XML content type.

OK, I see that now, but I thought text/xml was deprecated so wasn't valid for XHTML5 use, it seems I was wrong. Sorry about the false report :-)