From 66aa3011ee26ea27ec2b5461da647eaa9664f9d7 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Sat, 12 Jan 2013 12:24:05 +0000 Subject: [PATCH] Clarify the entry about the handling of duplicated Content-Type headers --- ChangeLog | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 9050fcd1..1400f447 100644 --- a/ChangeLog +++ b/ChangeLog @@ -75,9 +75,9 @@ ChangeLog for Privoxy - Allow HTTP/1.0 clients to signal interest in keep-alive through the Proxy-Connection header. While such client are rare in the real world, it doesn't hurt and couple of curl tests rely on it. - - Only remove duplicated headers when filters are enabled. If they are not it - doesn't cause ill effects and the user might not want it. While at it, - downgrade the removal message to LOG_LEVEL_HEADER to clarify that it's not + - Only remove duplicated Content-Type headers when filters are enabled. + If they are not it doesn't cause ill effects and the user might not want it. + Downgrade the removal message to LOG_LEVEL_HEADER to clarify that it's not an error in Privoxy and is unlikely to cause any problems in general. Anonymously reported in #3599335. - Accept a default-server-timeout of 0. It's the default after all. -- 2.39.2