- From: Jeffrey Yasskin <notifications@github.com>
- Date: Tue, 17 Apr 2018 15:51:27 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 17 April 2018 15:51:51 UTC
I also filed a similar issue as https://github.com/w3c/resource-hints/issues/78. As far as I can see, the flow is not specified and not tested in WPT. @kinu described the Chrome implementation as: 1. Page A embeds <link rel=prefetch href=B> 2. B is fetched as a subresource through A's Service Worker. If this is a real response (i.e. A's SW can't fake a cross-origin response), it's entered into a HTTP cache with a minimum 5-minute lifetime. 3. User clicks link to C. 4. If C requests B, that request goes through C's SW. 5. If C's SW forwards the request to the network, it'll find the prefetched response in the HTTP cache. -- 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/1302#issuecomment-382043843
Received on Tuesday, 17 April 2018 15:51:51 UTC