- From: Salvador de la Puente González <notifications@github.com>
- Date: Mon, 06 Jun 2016 06:51:37 -0700
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc:
Received on Monday, 6 June 2016 13:52:08 UTC
> 1. An error is thrown in the fetch listener and respondWith is not called (at the moment, I think the request will proceed to network) > 2. An error is thrown in the fetch listener and respondWith is called (at the moment, this depends on the value passed to respondWith) > 3. The resolved value passed to respondWith is not a response (at the moment, network error) > 4. The promise passed to respondWith rejects (at the moment, network error) I would fail on 3 and 4 and perhaps retry bypassing the worker on 1 and 2. From the programmable proxy perspective of the service worker, if that piece does not work, let the request continue to the network although if I'm explicitly passing a wrong type to the `respondWith`, let it fail. In any case, on failure, call `onerror()` for the `ServiceWorkerGlobalScope`. --- 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/892#issuecomment-223964849
Received on Monday, 6 June 2016 13:52:08 UTC