Re: [fetch] Add a bit to Opaque Responses to distinguish redirects (#79)

Sorry, I probably should stop responding on my phone :)

Yes, your solution sounds reasonable, but may not be future-proof. I think this will also become a problem:
onfetch=function(e){event.respondWith(fetch(e.request))}

And has nothing to do with Cache API, however, exploiting that would require a mechanism for me to create a cors-enabled navigational request, which AFAIK is impossible today (but might become possible in the future, one imaginary use-case could be to enable cross-origin <iframe seamless>, for example, although it's a strawman argument since seamless iframes are long gone crbug.com/229421)

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/79#issuecomment-125616932