- From: Ben Kelly <notifications@github.com>
- Date: Wed, 14 Aug 2019 08:22:38 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 14 August 2019 15:23:01 UTC
They use normal redirects today, but the problem is http cache eviction. Users often type vanity.com while offline and get a broken tab instead of redirected to the offline assets on actual.com. For the sites I've spoken to the vanity.com service worker solution would still result in a 301 response, just synthetically instead of from the network stack. In theory browsers could still integrate that into things like awesomebar. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1457#issuecomment-521293054
Received on Wednesday, 14 August 2019 15:23:01 UTC