diff --git a/RELEASENOTES.html b/RELEASENOTES.html index d7d87ca..e2fade6 100644 --- a/RELEASENOTES.html +++ b/RELEASENOTES.html @@ -1,11 +1,11 @@ - - Squid 3.2.6 release notes + + Squid 3.2.13 release notes -

Squid 3.2.6 release notes

+

Squid 3.2.13 release notes

Squid Developers


@@ -72,12 +72,14 @@ 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.2.6 for -testing.

+

The Squid Team are pleased to announce the release of Squid-3.2.13.

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

-

While this release is not deemed ready for production use, we believe it is ready for wider testing by the community.

+ +

A large number of the show-stopper bugs have been fixed along with general improvements to the IPv6 support. +While this release is not fully bug-free we believe it is ready for use in production on many systems.

+

We welcome feedback and bug reports. If you find a bug, please see http://wiki.squid-cache.org/SquidFaq/BugReporting for how to submit a report with a stack trace.

@@ -86,7 +88,7 @@ report with a stack trace.

Although this release is deemed good enough for use in many setups, please note the existence of -open bugs against Squid-3.2.

+open bugs against Squid-3.2.

Some issues to note as currently known in this release which are not able to be fixed in the 3.2 series are:

@@ -160,7 +162,7 @@ only to the original destination IP the client was requesting or to explicit pee DNS lookups to locate alternative DIRECT destinations will not be done.

Known Issue: When non-strict validation fails Squid will relay the request, but can only do -so safely to the orginal destination IP the client was contacting. The client original +so safely to the original destination IP the client was contacting. The client original destination IP is lost when relaying to peers in a hierarchy. This means the upstream peers are still at risk of causing same-origin bypass CVE-2009-0801 vulnerability. Developer time is required to implement safe transit of these requests. @@ -253,7 +255,7 @@ in front of the name of whichever helper is being multiplexed. It takes the help path and parameters as its own command parameters. The concurrency setting already existing in Squid is used to configure how many child helpers it may run.

-

For example, a traditional configration is +

For example, a traditional configuration is

         url_rewrite_program /your/redirector.sh
         url_rewrite_children 5
@@ -289,10 +291,10 @@ will be needed to be solved before starting Squid in production use.

The on-demand helpers feature allows greater flexibility and resolves this problem by allowing maximum, initial and idle thresholds to be configured. Squid will start the initial set during start and reconfigure phases. However over the operational use new helpers up to the maxium will -be started as load demands. The idle threshold determins how many more helpers to start if the +be started as load demands. The idle threshold determines how many more helpers to start if the currently running set is not enough to handle current request loads.

-

For example, a traditional configration is +

For example, a traditional configuration is

         auth_param ntlm /usr/libexec/squid/ntlm_auth
         auth_param ntlm children 200
@@ -357,7 +359,7 @@ For several helpers the directory name used in --enable-X-helpers configure opti