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

Also consider that the worker environment creation URL is set based on the worker global scope's URL which reflects redirects.  It seems we should probably reflect redirects here as well.

Of course, the worker creation URL is only set after following all redirects and not at each redirect step.  It also doesn't give us the opportunity to create a new Client on each redirect since fetch spec handles the redirections.

The fact that workers are same-origin avoids issues with cross-origin postMessage(), though.

I guess there is an open question here about how close we need to keep worker and window Client behavior to each other.  Closer seems better, though.

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