ISSUE-71 - Public View

setRequestHeader has too many header restrictions

State:
CLOSED
Product:
XMLHttpRequest
Raised by:
Anne van Kesteren
Opened on:
2006-04-06
Description:
http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/#dfn-setrequestheader
introduces a lot of restrictions on HTTP headers which we agreed upon to remove
(at least partially) during our first F2F (Oslo, 2006). People have been arguing
for removing at least the following headers from that list:

* Accept-Charset
* Accept-Encoding
* If-Modified-Since
* If-None-Match
* If-Range
* Range
* User-Agent

I think we also agreed upon some special behavior around If-Modified-Since. That
when the author has not set it the UA MUST always return a 200 (if nothing else
went wrong) with a full body (the UA can still set it for speeding up things
obviously), but if the author did set it and the server version is not newer the
UA MUST return a 304 (again, if nothing else went wrong).

I think I'll just go ahead and make some changes to the editor's draft to make
the changes outlined above unless someone objects...

Note: Some of these links may be accessible only to W3C Members.

Related emails:
  1. ISSUE-71: setRequestHeader has too many header restrictions (from dean+cgi@w3.org on 2006-04-06)
  2. Re: ISSUE-71: setRequestHeader has too many header restrictions (from ian@hixie.ch on 2006-04-06)
  3. Re: ISSUE-71: setRequestHeader has too many header restrictions (from annevk@opera.com on 2006-04-07)
  4. Re: ISSUE-71: setRequestHeader has too many header restrictions (from bzbarsky@mit.edu on 2006-04-07)
  5. Re: ISSUE-71: setRequestHeader has too many header restrictions (from jonas@sicking.cc on 2006-04-07)
  6. Re: ISSUE-71: setRequestHeader has too many header restrictions (from ian@hixie.ch on 2006-04-07)
  7. Re: ISSUE-71: setRequestHeader has too many header restrictions (from ian@hixie.ch on 2006-04-07)
  8. Re: ISSUE-71: setRequestHeader has too many header restrictions (from jim@jibbering.com on 2006-04-07)
  9. ISSUE-80: Default Content-Type header for POST (and other) requests (from dean+cgi@w3.org on 2006-05-03)
  10. Minutes, face to face meeting (from chaals@opera.com on 2006-05-15)

Related notes:

2006-05-14: Lets defer this to the "Headers / cache" proposal from mnot (2006, May).