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

> we still end up with a situation where we we're going to be sending down unneeded data on every request

I agree that's not ideal, but how much additional data are you planning on sending? And what will that data be?

> 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.

If we want this header to be updated outside of the service worker lifecycle it puts developers in a weird position, as the code for activating this feature can get out of sync with the fetch handling code. If they activate this feature and their fetch event doesn't cater for it, they can end up with two HTTP requests per navigation rather than one.

> Cookies seem like a hack here

Cookies already exist for storing state and sending it to the server, creating another thing which does that feels like a hack.

-- 
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-246998416