- From: Jon Walsh <notifications@github.com>
- Date: Fri, 03 Jun 2016 03:54:04 -0700
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc:
Received on Friday, 3 June 2016 10:54:30 UTC
> 200 is absolutely allowed as a response to a ranged request; servers aren't required to support them. Glad to know, but... > They seems to allow. Saw this many times our CDN, it returns 200 for ranged requests and browsers work fine. I wish this were true, but it doesn't seem like Chrome is currently doing this with Audio element. I've [documented this](http://stackoverflow.com/questions/37612177/cannot-play-cached-audio-from-service-worker), and would appreciate confirmation as to whether: 1. my bad, 2. Chrome's bad, 3. SW's bad --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/703#issuecomment-223549877
Received on Friday, 3 June 2016 10:54:30 UTC