Re: [whatwg/fetch] Cannot get next URL for redirect="manual" (#763)

Say the user navigates to `/test`. The service worker for that scope intercepts the fetch and forwards it to the server. The server responds with a redirect to `/somewhere-else`. If the service worker returns that redirect the browser will then navigate to /somewhere-else`, potentially hitting the same service worker or another. (The service worker could store these responses so this kind of redirect would also function offline.)

Note that typically redirects are followed for fetches (e.g., from `<img>`, `<script>`, `fetch()` by default), but navigation explicitly doesn't want to follow redirects because we might want to ask a different service worker to handle the request as the scope or origin can change.

Note that the browser does get to see the contents of the redirect, but nobody else does per the aforementioned link.

-- 
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/issues/763#issuecomment-397303809

Received on Thursday, 14 June 2018 13:53:42 UTC