- From: Jasper Magick <jasper.magick@gmail.com>
- Date: Wed, 21 Mar 2007 20:21:59 -0400
- To: www-validator@w3.org
> > So it effectively /is/ claiming to support XHTML, but your content > negotiation system is putting a higher priority on HTML. Some user agents don't advertise what they support in the accept header, that's why the priority is on HTML. If a user agent sends an incomplete accept header, and you send it "application/xhtml+xml" but it doesn't support it, the user agent will simply present you with a download dialog. So having the priority on HTML insures that those user agents that only support "text/html" get that if they fail to supply a complete accept header.
Received on Thursday, 22 March 2007 00:22:18 UTC