W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: [XHR] Redirects

From: Adam Barth <w3c@adambarth.com>
Date: Fri, 17 Sep 2010 10:27:01 -0700
Message-ID: <AANLkTik000eZi4cMGScxVHbYJkCSLmgVDOEW9f6C8Wbs@mail.gmail.com>
To: Darin Fisher <darin@chromium.org>
Cc: Julian Reschke <julian.reschke@gmx.de>, Anne van Kesteren <annevk@opera.com>, Boris Zbarsky <bzbarsky@mit.edu>, WebApps WG <public-webapps@w3.org>
On Thu, Sep 16, 2010 at 3:25 PM, Darin Fisher <darin@chromium.org> wrote:
> On Thu, Sep 16, 2010 at 6:31 AM, Julian Reschke <julian.reschke@gmx.de>
> wrote:
>>>> I think that obtaining the resolved Location for the redirect is the
>>>> most tricky part, and we should come up with a solution where that is
>>>> also available for people who do not want the default browser behavior.
>>> I don't really like special casing the Location header here. It seems we
>>> are ending up with two additional members for dealing with redirects. I
>>> do not want another one. There are other headers where resolving a URL
>>> might be needed. Adding a parameter to navigator.resolveURL() for a base
>>> URL is the way to go I think.
>> That sounds good to me. In general I think it would be great if there were
>> standard APIs for URI/IRI construction, parsing and resolution...
> Yes, that sounds pretty good to me too.

This has annoyed me for a while too.  I'll write up a spec.

Received on Friday, 17 September 2010 17:28:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:11 UTC