- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 22 Sep 2009 12:48:01 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7697 Mike Kelly <mike@mykanjo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mike@mykanjo.co.uk --- Comment #2 from Mike Kelly <mike@mykanjo.co.uk> 2009-09-22 12:48:01 --- Ian that would appear to be incorrect given that, according to the HTTP spec, the Accept header is simply intended to indicate the appropriate media types for a response to a given request: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html "The Accept request-header field can be used to specify certain media types which are acceptable for the response" So, the value of the Accept header should be taken (if specified) from the type attribute for a given hyperlink element - which is presumably why firefox modifies the accept header for the style and script elements. This allows hyperlinks to specific representations that must be negotiated via HTTP content negotiation - as it stands, it is not possible to specify such a link with HTML5. i.e. currently - these links would actually generate identical requests with the same Accept header: <a type='application/xml' href='/document'>document in xml</a> <a type='application/json' href='/document'>document in json</a> If implemented any existing mechanisms which disregard the Accept header would remain unaffected by the change. If no type is specified then default UA Accept header value should be assumed. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 22 September 2009 12:48:11 UTC