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

Correct me if I'm not understanding it correctly. The basic rule is the request url fragment propagates. But fragments given in Location urls will replace if it redirects. If response url's fragment is not null, that's the final value. Else, the request url's fragment propagates.

I think a response returned from SW to fetch is just a response. So, following the rule, if it has a fragment, that should be the last value. Else, the response url should get the request url's fragment.

E.g.
```js
e.request.url: 'foo#bar'
onfetch = e => { e.respondWidh(fetch('foo#baz')) };
```
The client should get response.url === 'foo#baz' (am I right?)

For the Cache behavior, whether we should strip response url's fragment before storing it by default, I think we should be consistent with what HTTP Cache does.

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