-Changes to squid-3.1.20 (08 Jun 2011):
+Changes to squid-3.1.21 (23 Sep 2012):
+
+ - Bug 3622: peerClearRRStart scheduling multiple events
+ - Bug 3615: configure check for default max number of FDs is broken
+ - Bug 3607: --enable-auth documented default action incorrect
+ - Bug 3593: socket failure: Address family not supported by protocol
+ - Bug 3584: Detection of setresuid() is broken
+ - Bug 3568: Consolidate external_acl_type config dumping and add missing %%
+ - Bug 3564: eCAP not supporting CoAP URI schemes
+ - Bug 3484: Docs: sslproxy_cert_error example flawed
+ - Bug 3462: Delay Pools and ICAP
+ - Bug 3133: better fix: Memory leak handling requests for sites that don't exist
+ - Bug 2976: ERR_INVALID_URL for transparently captured requests when reconfiguring
+ - Silence IOS 15.1 unknown capabilities messages.
+ - Account for Store disk client quota when bandwidth-limiting the server.
+ - ... and several documentation fixes
+ - ... and several compile fixes
+
+Changes to squid-3.1.20 (08 Jun 2012):
- Regression Bug 3545: FreeBSD dnsserver segfaults
- Regression Bug 3504: clientside_tos fails to mark traffic
- Support CoAP over HTTP (coap:// and coaps:// URLs)
- Support for 3.2 error template codes
-Changes to squid-3.1.19 (06 Feb 2011):
+Changes to squid-3.1.19 (06 Feb 2012):
- Regression Bug 3441: part 2: Prevent further cache size corruption of swap.state
- Bug 3473: erase last uses of obsolete auth_user_hash_pointer
dnl
dnl $Id$
dnl
-AC_INIT([Squid Web Proxy],[3.1.20-BZR],[http://www.squid-cache.org/bugs/],[squid])
+AC_INIT([Squid Web Proxy],[3.1.21-BZR],[http://www.squid-cache.org/bugs/],[squid])
AC_PREREQ(2.61)
AC_CONFIG_HEADERS([include/autoconf.h])
AC_CONFIG_AUX_DIR(cfgaux)
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
- <TITLE>Squid 3.1.20 release notes</TITLE>
+ <TITLE>Squid 3.1.21 release notes</TITLE>
</HEAD>
<BODY>
-<H1>Squid 3.1.20 release notes</H1>
+<H1>Squid 3.1.21 release notes</H1>
<H2>Squid Developers</H2>
<HR>
<HR>
<H2><A NAME="s1">1.</A> <A HREF="#toc1">Notice</A></H2>
-<P>The Squid Team are pleased to announce the release of Squid-3.1.20</P>
+<P>The Squid Team are pleased to announce the release of Squid-3.1.21</P>
<P>This new release is available for download from
<A HREF="http://www.squid-cache.org/Versions/v3/3.1/">http://www.squid-cache.org/Versions/v3/3.1/</A> or the
<A HREF="http://www.squid-cache.org/Mirrors/http-mirrors.html">mirrors</A>.</P>
<P>
<UL>
<LI>The lack of some features available in Squid-2.x series. See the regression sections below for full details.</LI>
+<LI>eCAP library version 0.2.0 and later are not supported. See eCAP section below for details.</LI>
+<LI>CVE-2009-0801 : NAT interception vulnerability to malicious clients. This is fixed in 3.2 series.
+Some attempts have been made to port for 3.1, but the unreliability of NAT handling in 3.1 makes this unsafe.</LI>
</UL>
</P>
<P>Currently known issues which only depends on available developer time and may still be resolved in a future 3.1 release are:</P>
<P>
<UL>
-<LI>CVE-2009-0801 : NAT interception vulnerability to malicious clients. This is fixed in 3.2 series.</LI>
<LI>Windows support is still largely missing.</LI>
<LI>AIX support for building with the IBM compiler is broken.</LI>
<LI>OpenSSL 1.0.0 support is incomplete.</LI>
<P>Currently known and available eCAP modules are listed in the wiki feature page on eCAP.</P>
+<P><EM>Known Issue:</EM> libecap version 0.0.3 (exactly) is required to build this series
+of Squid. Other versions of libecap contain significant interface differences.</P>
+
<H2><A NAME="ss2.10">2.10</A> <A HREF="#toc2.10">ICAP Bypass and Retry enhancements</A>
</H2>
RFC2475, and RFC3260.
The TOS/DSCP byte must be exactly that - octet value 0x00-0xFF.
- Note that in practice often only values up to 0x3F are usable
- as the two highest bits have been redefined for use by ECN
- (RFC3168).
+ Note that in practice often only multiples of 4 is usable as the
+ two rightmost bits have been redefined for use by ECN (RFC 3168
+ section 23.1).
+
+ Note that in practice often only values up to 0xFC are usable,
+ and only in multiple of 4, as the two rightmost bits have been
+ redefined for use by ECN (RFC3168).
This setting is configured by setting the source TOS values:
<!doctype linuxdoc system>
<article>
-<title>Squid 3.1.20 release notes</title>
+<title>Squid 3.1.21 release notes</title>
<author>Squid Developers</author>
<abstract>
<sect>Notice
<p>
-The Squid Team are pleased to announce the release of Squid-3.1.20
+The Squid Team are pleased to announce the release of Squid-3.1.21
This new release is available for download from <url url="http://www.squid-cache.org/Versions/v3/3.1/"> or the <url url="http://www.squid-cache.org/Mirrors/http-mirrors.html" name="mirrors">.
RFC2475, and RFC3260.
The TOS/DSCP byte must be exactly that - octet value 0x00-0xFF.
- Note that in practice often only values up to 0x3F are usable
- as the two highest bits have been redefined for use by ECN
- (RFC3168).
+ Note that in practice often only multiples of 4 is usable as the
+ two rightmost bits have been redefined for use by ECN (RFC 3168
+ section 23.1).
+
+ Note that in practice often only values up to 0xFC are usable,
+ and only in multiple of 4, as the two rightmost bits have been
+ redefined for use by ECN (RFC3168).
This setting is configured by setting the source TOS values:
projects / thirdparty / squid.git / commitdiff
