Re: [ServiceWorker] if service-worker-allowed header changes should active worker be potentially unregistered? (#857)

There was some back and forth in #604 . Eventually we settled on not unregistering. That was partly to be consistent with other HTTP response changes like MIME type becoming invalid or response code becoming 4**, which don't unregister.

I think there's still interest in a easier kill switch than skipWaiting() + unregister(). That's tracked at #614 

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