Send Accept-Ranges-header for file-requests
Now that the range-support is actually working, we can send out the Accept-Ranges-header so that clients know they can send range-requests to the server. This can be seen empirically when watching a video and skipping around into unbuffered space. Previously, it would not be possible and the time-selector would flip back to the furthest point the previous buffering had progressed. Now it is working flawlessly. Signed-off-by: Laslo Hunhold <dev@frign.de>
This commit is contained in:
parent
db4e35d3d5
commit
5a7994bc61
1 changed files with 2 additions and 1 deletions
3
resp.c
3
resp.c
|
@ -190,7 +190,8 @@ resp_file(int fd, char *name, struct request *r, struct stat *st, char *mime,
|
||||||
"Connection: close\r\n"
|
"Connection: close\r\n"
|
||||||
"Last-Modified: %s\r\n"
|
"Last-Modified: %s\r\n"
|
||||||
"Content-Type: %s\r\n"
|
"Content-Type: %s\r\n"
|
||||||
"Content-Length: %zu\r\n",
|
"Content-Length: %zu\r\n"
|
||||||
|
"Accept-Ranges: bytes\r\n",
|
||||||
s, status_str[s], timestamp(time(NULL), t1),
|
s, status_str[s], timestamp(time(NULL), t1),
|
||||||
timestamp(st->st_mtim.tv_sec, t2), mime,
|
timestamp(st->st_mtim.tv_sec, t2), mime,
|
||||||
upper - lower + 1) < 0) {
|
upper - lower + 1) < 0) {
|
||||||
|
|
Loading…
Reference in a new issue