W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2011

Re: Redirects and headers

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 05 Jul 2011 11:36:45 +0200
To: "Julian Reschke" <julian.reschke@gmx.de>, "Darin Fisher" <darin@chromium.org>
Cc: "Mark Baker" <distobj@acm.org>, "HTTP WG" <ietf-http-wg@w3.org>, "Mark Nottingham" <mnot@mnot.net>
Message-ID: <op.vx43njyg64w2qv@annevk-macbookpro.local>
On Mon, 04 Jul 2011 20:06:55 +0200, Darin Fisher <darin@chromium.org>  
wrote:
> It seems like XHR's followRedirects attribute gives devs enough control
> here.  XHR should at least document default header propagation behavior  
> if HTTP will not.

followRedirects is out for now.

Anyway, there are plenty of other APIs too, e.g. EventSource. And even if  
we added functionality to XMLHttpRequest we would still need to define the  
default. Adding more features does not solve any existing problems.

And if this decision is entirely up to the APIs, please have the HTTP  
specification say so. E.g. "Note: Clients will have to decide which  
headers sent in the original request are used in the request to the  
redirected location."


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Tuesday, 5 July 2011 09:37:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:44 GMT