Re: Validator lacks application/xml+xhtml in ACCEPT_HTTP

On Thu, 11 Mar 2004, Tõnu Samuel wrote:

 

> If I validate my pages using validator.3w.org, it falls back to HTML,

  it means

> validator lacks ACCEPT_HTTP=application/xml+xhtml in headers.

 

Pedantic detail: that's just Accept:

 

>             I believe it

> would be nice to have it there as validator can cope with XHTML well.

 

The validator is happy with XHTML.  It just doesn't do

content-negotiation.  If you want to validate content-negotiated pages,

you'll need to use Page Valet's Advanced form (which is part of the

subscription service only).

 

-- 

Nick Kew

 

The Validator should however do Content-Negotiation; since the help it
offers for a mime-type mismatch points to an article on how to setup your
script to detect if the browser supports the application/xhtml+xml
mime-type; and to output text/html if it doesn’t.  Since this is offered as
a solution to a problem with the validator; and it looks at the accept
header; shouldn’t the validator also use the accept header to let the page
know that it works with that kind of data?

 

~Navarr Barnier