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

After reviewing the WPT tests I kind of feel like we should match non-sw redirect behavior here.  So a fragment in the SW-provided response.url would override the request.url.  Cache pollution would be a potential problem, but sites can avoid that by storing responses without the fragment if they need to.  (They can purposely strip the request fragment when fetching the response to store in cache_storage, etc.) 

Not sure this is a hill I'm willing to die on, but I'm leaning more towards that solution than having redirects and respondWith() diverge in behavior.

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