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

Protocols/APIs and redirects

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 06 Dec 2011 12:14:24 +0100
To: "HTTP WG" <ietf-http-wg@w3.org>
Message-ID: <op.v52euanp64w2qv@annevk-macbookpro.local>
When we design APIs (XMLHttpRequest) and protocols (CORS) that support  
transparent redirects (redirects automatically followed by the API) what  
exactly should count as a redirect as far as they are concerned?  
Everything in the 3xx range that contains a Location header?

E.g. for some part of CORS  
http://dvcs.w3.org/hg/cors/raw-file/tip/Overview.html#actual-request we  
explicitly fail if the response code is 301, 302, 303, or 307, because we  
want the ability to support transparent redirects going forward. Should we  
also fail if the response code is 310?

Should  
http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#same-origin-request-event-rules  
follow redirects for status codes other than 301, 302, 303, and 307?  
Should it instead treat anything else as a network error so we can more  
easily extend it in the future? If we do not treat it as a network error  
the developer would just get back a response with a status code of 310 and  
the Location header and going forward we could never treat it as any of  
the "blessed redirects" anymore.


Aside: What happened to  
http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/0014.html ? I  
could not find the issue.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Tuesday, 6 December 2011 11:14:57 GMT

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