-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] Add the explanation on how LeoFS handle streaming media #1098
Comments
mp4 also can't be load by video.js URL :http://backet01.leofs.mydomain.com:8080/2.mp4 Connection: keep-alive |
@FunnyRyan It looks like uploading "2.mp4" failed because the response header from LeoFS included Content-Length: 0 so uploading the "2.mp4" file may fail (or just uploading 0 byte size for some reason). Can you tell us how you uploaded the file?
|
I uploaded this video again with DragonDisk, still can't play it. But the picture can be accessed |
@FunnyRyan Thanks for sharing the accessible links. I did sniff HTTP req/res and It seems LeoFS respond to GET with Range requests properly however the client (video.js) don't think of the response from LeoFS as valid ones. Since LeoFS may violate the HTTP spec regarding Range/Content-Range headers, I will look into the issue further. |
@FunnyRyan It seems that on my dev-box
So there might be problems related to Chrome. |
Product managers and programmers are playing because of functional requirements I can't play it on my phone or PC Chrome but working on IE...or Media Player |
I see. It seems that working environments (IE, Edge, Firefox) issue GET and get the full content through 200 response OTOH NOT working envs (Chrome etc) issue GET with Range and get the full content through 206 response so the latest Chrome doesn't think of the 206 response from LeoFS as valid one for some reason. I'll get back to you once I find the root problem. Memo: HTTP headers sniffed by DevTools
|
@FunnyRyan it turns out that I can play the video (2.mp4) on Chrome. so let me ask you about your system
On my dev-box,
works as expected with LeoFS 1.4.1 and 1.4.2 on Ubuntu 16.04. |
soft version : my Browser version was: Chrome<-> LeoGateway <-> LeoStorage |
@FunnyRyan Thanks. I will try to reproduce with the environment almost similar to yours. |
@FunnyRyan Also I may ask you make http://backet01.leofs.xiaohost.com:8080/2.mp4 accessible again when I fail to reproduce the issue with your setting on my dev-box in order to capture the packets flowed between the browser and LeoGateway. |
I uploaded another mp4 video yesterday, and the strange thing is that it works. |
@FunnyRyan OK. Let me know once you finish to test on the new cluster. |
It is seem to be stable now.....i used a unsupported version of Erlang 19.3......so i change it to 18.3 on centos7. this is the video which doesn't play on chrome last time i building on single servers |
There has been questions about how LeoFS handle streaming media files at
so it'd be good to have the explanation about it on the official docs.
The text was updated successfully, but these errors were encountered: