enjoying seafile for a while now. Just found that the video seek/skip is not working on the browser. I thought it had been supported since the recent introduce of byte-range feature. Would it be the configuration issue on my server?
Just found that the video seek/skip is not working on the browser.
Can you explain more about what did you observe when it “not working”?
Can you check if there is any error message in chrome/firefox’s debug console?
Also, are you running seafile server behind apache or nginx? If so, please check the apache/nginx logs on your server.
Looks like byte range requests do not work (as I understood it).
each time I clicked anywhere on the progress bar of the video player, the video player reset itself back to the beginning. I did not saw anything (no error message) on the console output.
Here is a piece of the access log of my nginx server. No error ouput in the error log.
180.164.176.78 - - [21/Feb/2017:17:05:04 +0000] "GET /notification/list/ HTTP/1.1" 200 2824 "http://example.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"
180.164.176.78 - - [21/Feb/2017:17:05:07 +0000] "GET / HTTP/1.1" 200 22449 "http://example.com/notification/list/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"
180.164.176.78 - - [21/Feb/2017:17:05:08 +0000] "GET /ajax/unseen-notices-count/?_=1487696708275 HTTP/1.1" 200 22 "http://example.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"
180.164.176.78 - - [21/Feb/2017:17:05:08 +0000] "GET /api/v2.1/groups/1/?_=1487696708276 HTTP/1.1" 200 236 "http://example.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"
180.164.176.78 - - [21/Feb/2017:17:05:08 +0000] "GET /api2/groups/1/repos/?from=web&_=1487696708277 HTTP/1.1" 200 1705 "http://example.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"
180.164.176.78 - - [21/Feb/2017:17:05:08 +0000] "GET /api2/groups/1/discussions/?avatar_size=64&_=1487696708278 HTTP/1.1" 200 876 "http://example.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"
180.164.176.78 - - [21/Feb/2017:17:05:20 +0000] "GET /ajax/unseen-notices-count/?_=1487695278817 HTTP/1.1" 200 22 "http://example.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"
180.164.176.78 - - [21/Feb/2017:17:05:22 +0000] "GET /lib/2e639843-655f-4c11-adb5-aab214b23d29/file/test.mp4 HTTP/1.1" 200 9236 "http://example.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"
180.164.176.78 - - [21/Feb/2017:17:05:42 +0000] "GET /api2/ping/ HTTP/1.1" 200 16 "-" "Mozilla/5.0"
180.164.176.78 - - [21/Feb/2017:17:05:42 +0000] "GET /api2/account/info/ HTTP/1.1" 200 156 "-" "Mozilla/5.0"
@daniel.pan Looks like when range requests are supported seafhttp should send a Accept-Ranges header.
We will check the problem.