From: Amos Jeffries Date: Thu, 13 Oct 2011 08:22:01 +0000 (-0600) Subject: Prep for 3.1.16 X-Git-Tag: SQUID_3_1_16~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=dbcfc49c53a57154a66c2291bceb3b73a3dc2185;p=thirdparty%2Fsquid.git Prep for 3.1.16 --- diff --git a/ChangeLog b/ChangeLog index deb8a51bcd..fa9a22f95d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,16 @@ +Changes to squid-3.1.16 (14 Oct 2011): + + - Bug 3373: invalid URL in ERR_CACHE_ACCESS_DENIED + - Bug 3368: Unhandled exceptions are not logged (workaround) + - Bug 3326: miss_access incorrect default + - Bug 3320: miss_access description confusing + - Bug 3241: squid_kerb_auth cross compilation fix + - Bug 3237: seq fault in free() from rfc1035RRDestroy + - Bug 3190: Large HTTP POST stuck after early ICAP 400 error response + - db_auth: display available DSN drivers on connect error + - Updated OpenSSL 1.0.0 version checks + - ... and several documentation fixes + Changes to squid-3.1.15 (28 Aug 2011): - Regression fix: vhost and defaultsite causing vport to be ignored @@ -140,7 +153,6 @@ Changes to squid-3.1.10 (22 Dec 2010): - ... and updated documentation - ... and some code optimization/simplification polish ->>>>>>> MERGE-SOURCE Changes to squid-3.1.9 (25 Oct 2010): - Bug 3088: dnsserver is segfaulting diff --git a/doc/release-notes/release-3.1.html b/doc/release-notes/release-3.1.html index c2f4486128..ddc2de2cda 100644 --- a/doc/release-notes/release-3.1.html +++ b/doc/release-notes/release-3.1.html @@ -2,10 +2,10 @@ - Squid 3.1.15 release notes + Squid 3.1.16 release notes -

Squid 3.1.15 release notes

+

Squid 3.1.16 release notes

Squid Developers


@@ -71,7 +71,7 @@ for Applied Network Research and members of the Web Caching community.

1. Notice

-

The Squid Team are pleased to announce the release of Squid-3.1.15

+

The Squid Team are pleased to announce the release of Squid-3.1.16

This new release is available for download from http://www.squid-cache.org/Versions/v3/3.1/ or the mirrors.

@@ -90,13 +90,13 @@ While this release is not fully bug-free we believe it is ready for use in produ

Currently known issues which only depends on available developer time and may still be resolved in a future 3.1 release are: