Re: [w3c/ServiceWorker] HTTPS request without origin header are not intercepted by Service Worker (Issue #1653)

The origin header is a bit of a distraction.  The real issue here is the Sec-Fetch-Mode header.  The "behavior 2" case above has `Sec-Fetch-Mode: navigate`.  (Downloads are navigations.)  Navigation requests match their URL against registration scope in order to find a service worker to handle a fetch event.  So in this case only a service worker owned by dl.boxcloud.com could intercept the navigation request.

This is all working as intended.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1653#issuecomment-1195852385
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1653/1195852385@github.com>