- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 04 Jan 2010 15:18:51 +0100
- To: Chris Double <cdouble@mozilla.com>
- CC: HTMLwg <public-html@w3.org>
Chris Double wrote: > On 5/01/2010, at 1:29 AM, Julian Reschke wrote: > >> Could you please clarify what "seekable" means in the context of HTTP resources? > > An Ogg resource served via HTTP is seekable if the HTTP server supports byte range requests. This is most easily determined if the server sends Accept-Ranges. Ok. > Some servers do not send that but still support byte ranges. Some of these (Amazon S3 for example) will respond with a 216 response code if you do a byte range request starting from 0 so they can be identified by making a range request on the first GET. You mean 206, right? That's what they are supposed to do. Best regards, Julian
Received on Monday, 4 January 2010 14:19:26 UTC