Jayr Motta
unread,May 16, 2013, 12:55:04 PM5/16/13Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to chromi...@chromium.org, Jayr Motta, Joe Marini, Chromium Apps
Joe,
Many topics and questions around the web are saying that requests made by the video tag has a byte range set, but when the server returns a partial content code (the range of bytes asked by the request) it sometimes fail to render/handle the bytes coming from the server. It seems just works for small videos.
The solution I've reading around is to somehow change the behavior of the server to return the status code 200 instead of 206 partial content and it would work properly. There are some problems with that:
1 - My first attempt was to load a video from the filesystem and getting the physical URL through the interface FileEntry method toURL(), but when I did I got some canceled requests and some ok (
http://i.imgur.com/oSFGBK2.png ).
2 - The second attempt was to set up an apache server and distribute the files through the webserver instead of accessing local files, them the whole problem with status codes and byte ranges came up.
I've observed that youtube returns 200 for video streams, maybe they had the same problem but as they are in another level in streaming videos and had to run over chrome they might overcame it by changing the status code (and went against the RFC I believe), but it really seems wrong.
Don't you think?