Re: [w3c/ServiceWorker] importScripts request does not include Service-Worker header (#1538)

Well, it looks natural. If a browser loads service worker script with this header (and it is mentioned in the spec), and the script's server can verify (a bit) the request, why it (browser) does not set the header if the request is initiated in another way, using 'importScripts' instead of 'register'?

In the current situation, the same functionality (service worker loading) looks not the same from the script's server point of view.
At least, it worth to mention the difference in the documentation or in the spec, or make clear that the header is optional.

-- 
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/1538#issuecomment-694250358