Hi Navneet,
To give a bit more background:
"Accept-Ranges: bytes" is super useful for situations like HTML5 video
playback (e.g. mp4, ogg, webm) on browsers like Chrome and Firefox -
they look for it to check if byte range is supported, then do a byte
range request to seek to the end of the file and check the duration of
the file. You can then start playing a video straight away. If the
server does not advertise the fact, playback is crappy as it can't
stream/play straight away as it has to buffer the whole file to figure
out the duration.
This is a very useful function - I know "Accept-Ranges: bytes" is not
mandatory according to the HTTP spec but it is useful to advertise the fact that Google Cloud Storage does support
byte range requests. Google Cloud Storage did this until a few days ago and had been doing it for some time!
Useful reference:
Thanks
James
On Monday, May 28, 2012 11:47:00 PM UTC+10, Navneet (Google) wrote:
Hi James,
We'll look into this.
So we understand the issue better - are byte range serving requests failing, or is it just the header that's missing? If the latter, could you help me understand the mechanisms that rely on the header (vs the functionality)?
Thanks,
Navneet
On Sun, May 27, 2012 at 10:03 PM, James Broberg wrote:
Hi guys,
Since 24 May 2012, responses to GET requests no longer contain the appropriate header directive to signify that you support byte range serving ("Accept-Ranges: bytes"). We have a daily unit test that runs over Google Cloud Storage which checks the headers for this directive.
Is there a reason why this was removed and can it be added back? We depend on this capability - it's especially useful when serving up HTML5 video as it allows arbitrary seeking in the video without some fancy pants streaming server.
Many thanks,
James