- From: Joseph Liccini <notifications@github.com>
- Date: Fri, 09 Mar 2018 21:36:58 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 9 March 2018 21:37:22 UTC
I do think we need some more recommendations / cookbooks around SW caching and authenticated experiences. I.e. things like - API calls by default will be cached as Request-Response pairs if using the `caches` API. -- That means `Authorization` headers with tokens will be persisted in cache unless developer takes action to delete that header before caching - Web Crypto for advanced security in IndexedDB / Caches API - Handling Logout flows - Multiple signed in users, detecting traffic and keying cache by user ID -- 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/909#issuecomment-371952160
Received on Friday, 9 March 2018 21:37:22 UTC