- From: Asa Kusuma <notifications@github.com>
- Date: Wed, 20 Jun 2018 16:09:14 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 20 June 2018 23:09:36 UTC
I like the idea of having an escape hatch for a misbehaving service worker via a header like `Clear-Site-Data`. Not requiring any any client intervention makes it a lot more foolproof. > It'd also clear a whole lot more, but maybe that's ok. I also think this is ok. I see this as a final safety measure, and in usage scenarios, it's probably best to clear any persistent data that might have been modified by the service worker. -- 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/614#issuecomment-398925571
Received on Wednesday, 20 June 2018 23:09:36 UTC