Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)

For SVG: everyone but Fx discards the fragment given in a `Location` header. Everyone respects a fragment in an "input" URL that ends up redirecting (copying it over to the final response). If both contain a fragment, only Firefox uses the one from the `Location` header, everyone else uses the fragment from the "input" URL.

So if non-Firefox browsers are willing to change, maybe we should just go with that as it matches what HTTP ended up with. We could then also change `fetch()` and `XMLHttpRequest` to start exposing the fragment (and have it exposed in service workers too).

cc @wanderview 

-- 
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/issues/505#issuecomment-361985220