Re: [ServiceWorker] what should the document base URI for an intercepted navigation (#787)

Unfortunately I don't think the answers were particularly useful, there's a lot of confusion around when `fetch()` would return a redirect and when it wouldn't.

Some developers are happy for the SW to act like a server, where it'd swallow redirect or deliberately serve redirects, but this can't work due to the security stuff around opaque redirects.

Despite some developers being happy with `event.respondWith(fetch(event.request))` breaking non-SW behaviour, I'm pretty sure it'll create angst if people try and use SW just to create offline fallback pages, and find that `event.respondWith(fetch(event.request).catch(…))` is causing difficult-to-debug differences. This was a mistake of appcache that I'm really against introducing.

Seems that whatever we pick here is going to be what a large number of developers do not expect, so for consistency reasons I'm happy to go for response url across the board, but a way to change it via a header or property on `response` (maybe just `response.url`?) would be nice.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/787#issuecomment-184167911