Foreign Fetch

[daviddias]

I've been reading more about Foreign Fetch to understand if it would be the feature we need in order to enable an IPFS Service Worker to capture all the ipfs.iorequests.

Foreign Fetch is the (experimental) feature that enables domain a.com to use the service worker from b.com

Unfortunately, as explained in -- https://developers.google.com/web/updates/2016/09/foreign-fetch --, an app or website needs to set the Origin-Trial token on their HTTP response, so that the browser is comfortable with using a Service Worker from another domain.

Plus, the service worker itself would have to allow each domain, see -- https://github.com/w3c/ServiceWorker/blob/master/foreign_fetch_explainer.md --. Essentially, this is like setting up CORS for your service worker.

[lidel]

Sadly Origin Trial of Foreign Fetch ended and the concept was removed from spec: w3c/ServiceWorker#1188

Based on recent research done by Irakli in arewedistributedyet/arewedistributedyet#32 a partial workaround based on Iframe+ServiceWorker might exist for some use cases.

We will look into that in ipfs/service-worker-gateway#30 (cc ipfs/in-web-browsers#55)

[daviddias]

Sadly Origin Trial of Foreign Fetch ended and the concept was removed from spec: w3c/ServiceWorker#1188

Such a huge missed opportunity. Seems that we failed to make the case for it.

Based on recent research done by Irakli in arewedistributedyet/arewedistributedyet#32 a partial workaround based on Iframe+ServiceWorker might exist for some use cases.

This sounds very similar to @kumavis and @frankiebee work for Metamask.