From: Fabian Keil <fk@fabiankeil.de>
Date: Sat, 12 Jan 2013 12:23:12 +0000 (+0000)
Subject: Remove a pipelining limitation that no longer applies
X-Git-Tag: v_3_0_20~52
X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=9b4b5ccdc1b49407835719ff0d56c9d25bbfbf0d

Remove a pipelining limitation that no longer applies
---

diff --git a/ChangeLog b/ChangeLog
index ef74d547..07dd3ed7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -32,8 +32,7 @@ ChangeLog for Privoxy
   - New directive tolerate-pipelining can be used to enable client-side
     pipelining. If enabled (3.0.20 beta enables it by default), Privoxy will
     keep pipelined client requests around to deal with them once the current
-    request has been served. At the moment this is only done if the current
-    request is known to have no body.
+    request has been served.
   - New --config-test option lets Privoxy exit after checking whether or not
     the configuration seems valid. The limitations noted in TODO #22 and #23
     still apply. Logging the problem to the logfile if one is configured and