Re: [fetch] Redirected range requests and preflights. (#145)

This scheme is already in use widely by CDNs. Chrome's HTMLMediaElement is stitching fragments served for different URLs together (see the opening comment of https://code.google.com/p/chromium/issues/detail?id=532569 by strobe). Chrome's resource loader in general doesn't.

Given the situation, it seems we could document requirements for such an approach to make sure it's secure. It doesn't necessarily require all "fetching" on the web platform to do the stitching.

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

Received on Thursday, 29 October 2015 07:59:42 UTC