Annevk: /* Modifications to Fetch */

2015-07-19T17:43:48Z

Modifications to Fetch

← Older revision		Revision as of 17:43, 19 July 2015
Line 6:		Line 6:

	On the face of it, it seems step 3, substep 5, of https://fetch.spec.whatwg.org/#http-fetch, needs modifications to check for a foreign fetch enabled service worker before going to the cache/network.		On the face of it, it seems step 3, substep 5, of https://fetch.spec.whatwg.org/#http-fetch, needs modifications to check for a foreign fetch enabled service worker before going to the cache/network.

			There also needs to be some kind of limit imposed so you can't get infinitely nested service workers (or loops). What exactly is best here is unclear.

	== API ==		== API ==

Annevk: Created page with "This is a proposal for invoking service workers for requests that are same-origin with the service worker fetched from cross-origin clients. == Modifications to Fetch == ......"

2015-07-07T10:09:45Z

Created page with "This is a proposal for invoking service workers for requests that are same-origin with the service worker fetched from cross-origin clients. == Modifications to Fetch == ......"

New page

This is a proposal for invoking service workers for requests that are same-origin with the service worker fetched from cross-origin clients.

== Modifications to Fetch ==

...

On the face of it, it seems step 3, substep 5, of https://fetch.spec.whatwg.org/#http-fetch, needs modifications to check for a foreign fetch enabled service worker before going to the cache/network.

== API ==

<pre>[Constructor (DOMString type, optional ForeignFetchEventInit eventInitDict),
Exposed=ServiceWorker]
interface ForeignFetchEvent : ExtendableEvent {
readonly attribute Request request;
};

dictionary ForeignFetchEventInit : ExtendableEventInit {
required Request request;
};

partial interface ServiceWorkerRegistration {
Promise<void> enableForeignFetch();
Promise<void> disableForeignFetch();
);</pre>

Note: We cannot extend FetchEvent because that exposes client and messaging functionality which might lead to security issues since current practice is all same-origin messaging when it comes to service workers.

== Link header ==

<pre>Link:</sw.js>;rel=serviceworker;scope=/;handles=fetch,foreignfetch,push</pre>

Foreign Fetch - Revision history

Annevk: /* Modifications to Fetch */

Annevk: Created page with "This is a proposal for invoking service workers for requests that are same-origin with the service worker fetched from cross-origin clients. == Modifications to Fetch == ......"