Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920)

Yes, with the "navigation-preload" header we can ensure that tell that something came from the Service Worker, but we still end up with a situation where we we're going to be sending down unneeded data on every request. There's data that only makes sense on preload from a service worker context so to me it makes sense that we'd just set and send them only from within the service worker.

Also, while this won't necessarily be a problem for us, cookies can be modified from both the window and via responses from the server. For developers who don't control their entire stack this could very well cause issues.

Cookies seem like a hack here, I think that being able to set data in a header makes more sense and brings preload's options more in line with what you can do with fetch today.

-- 
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/920#issuecomment-246916790