From: wessels <>
Date: Fri, 25 Sep 1998 12:02:57 +0000 (+0000)
Subject: update
X-Git-Tag: SQUID_3_0_PRE1~2629
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=71d6dc563a3bf3c7357c9080a4cb42d60f83b2e3;p=thirdparty%2Fsquid.git

update
---

diff --git a/ChangeLog b/ChangeLog
index cff8e5c5d7..89d4a21bee 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,5 @@
+Changes to Squid-2.0 (September 25, 1998):
+
 	- Added NAT/Transparent hijacking code from Quinton Dolan.
 	- Added actual filesystem usage to cachemgr 'storedir' page.
 	  Only works for some operating systems.
@@ -9,15 +11,17 @@
 	- Fixed off-by-one bug for dead neighbor detection (Joe Ramey).
 	- 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.
+		- 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):