- From: Jake Archibald <notifications@github.com>
- Date: Thu, 30 Mar 2017 18:13:07 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 31 March 2017 01:13:39 UTC
I've been thinking about this again, here's a brain dump: * I should run my [tests](https://docs.google.com/document/d/1SphP-WNxqzZrSv_6ApC9_FpM-m_tLzm57oL3SNGg-40/edit#heading=h.1k8r6xdc6vfo) again, but using a wav file, which would eliminate weirdness due to metadata being at the end of the file. (thanks @foolip!) * Research which APIs follow the validation rules for combining ranges https://tools.ietf.org/html/rfc7233#section-4.3 - @foolip suggests that media elements don't care, but what about other APIs? It would be pretty bad security-wise if some APIs didn't validate. * It's down to individual APIs to say if they can accept ranged requests, what type of validation they require, and what URL they're prepared to accept a response from. Eg, for the first part of a response, they may accept any url, but for further parts they may only accept responses from that url. -- 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/144#issuecomment-290588589
Received on Friday, 31 March 2017 01:13:39 UTC