- synced with Range support changes

- added X-Forwarded-For TODO entry

diff --git a/ChangeLog b/ChangeLog
index 834bbd299d8d8408bbe260b398475d3ad38e4c4f..0820f10f194a810175c1b8940bbb82b456c243b5 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -6,6 +6,18 @@
          Kbytes, not bytes.
        - Changed storeDirSelectSwapDir() to skip swap directories
          when their utilization is over the high water mark ratio.
+       - fixed bugs in Content-Range header generation
+       - changed the way Range requests are handled:
+               - do not "advertise" our ability to process ranges at all
+               - on hits, handle simple ranges and forward complex ones
+               - on misses, fetch the whole document for simple ranges
+                 and forward range request for complex ranges
+         The change is supposed to decrease the number of cases when clients
+         such as Adobe acrobat reader get confused when we send a "200"
+         response instead of "206" (because we cannot handle complex ranges,
+         even for hits) Note: Support for complex ranges requires storage of
+         partial objects.
+
 
 Changes to squid-1.2.beta25 (September 21, 1998):
 

diff --git a/TODO b/TODO
index a9f5a8fdce38372948e7b7497b748bfb80cd6fba..026edc1e9a0cc14147dfc985e774bc1895072e67 100644 (file)
--- a/TODO
+++ b/TODO
@@ -51,7 +51,7 @@ Our Todo List
 (5)    return "ERR_TOO_LARGE" messages for replies with
        content-lengths larger than some limit.
 (5)    Bind HTTP/ICP sockets to multiple interfaces
-(5)    multirange requests with out-of-order ranges (AR)
+(5)    Custom X-Forwarded-For
 
 DONE:
 + s/sprintf/snprintf/g