Re: [w3c/ServiceWorker] support efficient offline redirects (#1457)

Taking it a step back, how about caching redirect on same website. Say you wish to cache a unique url at start up for the user, which is returned as a redirect after login, e.g. `/login/` -> `/redirect/` -> `/some/default/url/123/`. It seems like if one tries to cache the `/redirect/` response in the service worker, it caches the `/some/default/url/123/` response instead. One should be able to specify to cache the followed redirect or the redirect itself. I hope this even makes sense.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1457#issuecomment-1047773939
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1457/1047773939@github.com>

Received on Tuesday, 22 February 2022 13:02:35 UTC