Re: [w3c/ServiceWorker] _Update algorithm should unregister SW on 404 and 410 errors (#204)

What if a 404/410 triggered a SW unregistration, but only on localhost origins?

The decision to close this issue made assumptions that we were dealing with a production server, using HTTPS, but this has become a recurring pain point for developers who are using SWs on a common localhost:port combination, e.g. `localhost:3000` or `localhost:8000`. As soon as the first project that uses a SW is registered, that SW will remain in control for subsequent navigations, even if the developer switches to a project that has no SW.

See https://github.com/facebookincubator/create-react-app/pull/2438, for one example of the attempts to work around this, but that type of one-off solution doesn't scale.

-- 
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/204#issuecomment-306941887