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

Personally I'd prefer to strip response url fragments in Cache API by default.  If there is a use case for preserving the fragment there we could add a `preserveFragment:true` option or something.

Also, I don't think we can get rid of propagating the request url fragment if the response url fragment is missing, regardless.  Consider the case where an install event handler adds a resource to the cache with no fragment, but every FetchEvent request does have a fragment.  The fragment should not be lost on those FetchEvents if you pull the response out of the cache.

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