You did not understand. A page accessed from the same URL, like mine http://indy.kamibu.com/ checks the HTTP Accept header the browser sends, and if that header includes the "application/xhtml+xml" MIME Type, then it sends XHTML 1.1, and Content-Type: "application/xhtml+xml". If that header does not contain that specific MIME TYPE, then that page is served as XHTML 1.0 Strict, and the Content-Type is "text/html". So, for better testing, the HTML Validator should include "application/xhtml+xml" in its HTTP Accept header. It is simple, I think ;-) On Thu, Dec 11, 2008 at 6:11 PM, olivier Thereaux <ot@w3.org> wrote: > > On 11-Dec-08, at 11:01 AM, Andreas Prilop wrote: > >> The browser gets "text/html" >> http://www.unics.uni-hannover.de/nhtcapri/ruby-annotation.x.html >> or it gets "application/xhtml+xml" >> http://www.unics.uni-hannover.de/nhtcapri/ruby-annotation.xhtml >> > > Right: it is often desireable to have a specific URI for each variant of a > format-negotiated resource. > > Not all techniques make it possible, however. The often-used "switch media > type for a single page depending on the browser", for instance, doesn't. > > -- > olivier > -- Programs must be written for people to read, and only incidentally for machines to execute.Received on Thursday, 11 December 2008 17:17:36 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 1 October 2009 14:49:11 GMT