- From: Ben Kelly <notifications@github.com>
- Date: Thu, 26 Oct 2017 19:41:18 +0000 (UTC)
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 26 October 2017 19:41:45 UTC
> Blink bug https://code.google.com/p/chromium/issues/detail?id=553535 @mattto @horo-t Has this been implemented in chrome? This issue still says "assigned", but this glitch test suggests the final Response.url is being synthesized across to the intercepted request: https://sw-passthrough-redirect.glitch.me/ In firefox I currently get: ``` ==> SW fetch() got Response url:https://sw-passthrough-redirect.glitch.me/final.txt redirected:true ==> window fetch() got Response url:https://sw-passthrough-redirect.glitch.me/redirect.txt redirected:false ``` In chrome I get: ``` ==> SW fetch() got Response url:https://sw-passthrough-redirect.glitch.me/final.txt redirected:true ==> window fetch() got Response url:https://sw-passthrough-redirect.glitch.me/final.txt redirected:true ``` Note that the window fetch() is seeing "final.txt". Is this a fetch() only thing right now in chrome, or have you implemented it for all intercepted network requests? I'm happy if this is implemented in chrome, because I'd like to fix: https://bugzilla.mozilla.org/show_bug.cgi?id=1222008 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/146#issuecomment-339778444
Received on Thursday, 26 October 2017 19:41:45 UTC