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

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 UTC