From 51d0fdce74aeb23ef28336037b2d35aa4c955cee Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Wed, 20 Dec 2023 14:08:25 +0000
Subject:  Major refactors; implement ranges

Signed-off-by: Laurent Bercot <ska@appnovation.com>
---
 doc/future.html | 17 -----------------
 1 file changed, 17 deletions(-)

(limited to 'doc')

diff --git a/doc/future.html b/doc/future.html
index 1a8c3e5..512f3b7 100644
--- a/doc/future.html
+++ b/doc/future.html
@@ -25,23 +25,6 @@ of HTTP that would be nice to have, and that may be implemented at some point
 down the line.
 </p>
 
-<h2> Ranges </h2>
-
-<p>
- <a href="https://datatracker.ietf.org/doc/html/rfc9110#section-14">Ranges</a>
-are a useful part of HTTP when you are serving big files and connections may
-be interrupted and restarted: supporting the <tt>Range:</tt> header can save
-bandwidth, if the client only asks for the parts of the files that it's still
-missing.
-</p>
-
-<p>
- It hasn't been implemented in tipidee yet because parsing the <tt>Range:</tt>
-header is rather complex, and serving parts of files (as opposed to full files
-sequentially) also requires some extra coding that wasn't deemed worth it for
-an initial release.
-</p>
-
 <h2> HTTP Basic Authentication </h2>
 
 <p>
-- 
cgit v1.3.1