- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 18 Nov 2013 19:06:16 +0100
- To: Anne van Kesteren <annevk@annevk.nl>, WebApps WG <public-webapps@w3.org>
On 2013-11-18 17:29, Anne van Kesteren wrote: > We discussed this briefly during TPAC. Currently you can only get to > the response URL if you are loading a document resource. The idea here > is to add a new property that exposes the response URL for any > resource. It will work the same way as status and statusText, as when > those are available we know we will no longer be redirected. > > Anyone see a problem with adding this feature? > > Prior discussion: https://www.w3.org/Bugs/Public/show_bug.cgi?id=15417 Providing the URI of the resource that the final HTTP request was submitted to sounds like a good idea. That being said, how about giving the caller more control over whether redirects are followed at all? (yes, broken record :-) Best regards, Julian
Received on Monday, 18 November 2013 18:06:45 UTC