Re: [w3c/ServiceWorker] reserved Client objects and redirected navigations (#1031)

>As an implementation note, I likely will have to do something like:
>
>    * Create the reserved Client object before the initial network request.
>    * On redirect mutate the existing Client object to the new origin/URL/ID and wipe any pending messages.
>    * Freeze the origin/URL/ID once the Client is marked as execution ready.
>
>I don't like this, but due to a number of implementation details its very very racy to handle redirects for worker threads any other way. The redirects happen on a different thread altogether.

FWIW, turns out I don't need to do this any more.  I was able to prove to myself that we don't allow cross-origin redirects for worker scripts even with our non-standard data URL handling in gecko.

So I will create a new Client where appropriate in firefox instead of mutating the existing one.

-- 
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/1031#issuecomment-277032060