Re: [whatwg/fetch] Stop censoring fragments (#696)

The reason I haven't merged this is because @wanderview raised some good concerns. In particular how this integrates with navigation and service workers.

It seems we could apply the same behavior there as HTTP does (forward the fragment if none is present; this also means the response fragment would win), but this does mean that the response's URL is mutated for service worker responses, if I'm not mistaken (we cannot add a URL to the URL list either as that would lead the response to counting as being redirected).

Mutating the URL of the original response would be especially problematic, so we'd probably have to clone and mutate the clone?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/696#issuecomment-415394498