- From: Matt Falkenhagen <notifications@github.com>
- Date: Sun, 26 Mar 2017 22:19:58 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 27 March 2017 05:20:32 UTC
fetch-event.https.html has a test for the referrer policy, but Chrome won't pass it because it blocks mixed content fetches by default. The test performs a fetch to an http URL from an https iframe. It expects the service worker to receive a fetch event whose request has a `referrerPolicy` of `"no-referrer-when-downgrade"`. However in Chrome, the fetch() will reject, with an accompanying Mixed Content warning in the console. We could get around this by adding Chrome-specific configuration to the web platform test: ``` if (window.testRunner) testRunner.overridePreference('WebKitAllowRunningInsecureContent', true); ``` But this seems unfortunate. Questions: - Does the Mixed Content spec allow Chrome to do this? - If so, is there a better way to test behavior in the web platform test without adding Chrome-specific code? cc/ @mkwst @yutakahirano -- 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/1094
Received on Monday, 27 March 2017 05:20:32 UTC