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: Fri, 7 Apr 2006 20:27:51 +0000 (UTC)
To: Jonas Sicking <jonas@sicking.cc>
Cc: Web APIs WG <public-webapi@w3.org>
Message-ID: <Pine.LNX.4.62.0604072027180.21459@dhalsim.dreamhost.com>

On Fri, 7 Apr 2006, Jonas Sicking wrote:
>
> Ian Hickson wrote:
> > 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.
> 
> The use-case that was brought up for Accept-Charset was that someone may 
> want an ascii-only result back.

...well then they should change their server to only send back an ASCII 
result...

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 7 April 2006 20:28:02 GMT

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