W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

Re: ISSUE-71: setRequestHeader has too many header restrictions

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 6 Apr 2006 22:09:06 +0000 (UTC)
To: Web APIs WG <public-webapi@w3.org>
Message-ID: <Pine.LNX.4.62.0604062143520.21459@dhalsim.dreamhost.com>

On Thu, 6 Apr 2006, Web APIs Issue Tracker wrote:
>
> * Accept-Charset
> * Accept-Encoding

These it makes no sense to remove. They're only useful for the UA because 
the UA is the one that's gonna handle the charset and encoding aspects.


> * If-Modified-Since
> * If-None-Match
> * If-Range

I am fine with these being allowed, IF the spec defines what should happen 
in the case where the server returns a 304 but the client doesn't have the 
relevant file in its cache.


> * Range

How would this work for XML MIME types?


> * User-Agent

I would ask that we only allow additions to this one.


> 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 guess that makes sense.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 6 April 2006 22:09:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT