quark

commit 5a7994bc61ce868521fc996e46006b61d07d23c4
parent db4e35d3d5cbd5bfac61cfb8edadd47c4608a864
Author: Laslo Hunhold <dev@frign.de>
Date:   Thu, 23 Jul 2020 18:54:43 +0200

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>

Diffstat:
M
resp.c
 | 
3
++-

1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/resp.c b/resp.c
@@ -190,7 +190,8 @@ resp_file(int fd, char *name, struct request *r, struct stat *st, char *mime,
 	            "Connection: close\r\n"
 	            "Last-Modified: %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),
 	            timestamp(st->st_mtim.tv_sec, t2), mime,
 	            upper - lower + 1) < 0) {