- From: Salvador de la Puente González <notifications@github.com>
- Date: Thu, 07 Jan 2016 04:58:31 -0800
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Thursday, 7 January 2016 12:59:02 UTC
Currently, trying to fetch content served by HTTP inside a service worker results in the request being blocked by the UA. Is this the expected behaviour? If so, which parts of the current specification support it? I found this comment in a Chrome bug, referring to that: https://code.google.com/p/chromium/issues/detail?id=448672#c4 It says fetch is not an optionally blockable request context but the [_should fetching request be blocked as mixed content_ algorithm](https://w3c.github.io/webappsec-mixed-content/#should-block-fetch) and [should response to request be blocked as mixed content](https://w3c.github.io/webappsec-mixed-content/#should-block-response) state [passthrough requests](https://w3c.github.io/webappsec-mixed-content/#passthrough-request) should be **allowed** (maybe with an opaque response, but that's another story). --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/813
Received on Thursday, 7 January 2016 12:59:02 UTC