[squid-users] Squid 3.3.2 is available

The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.3.2 release!

  Please note that with 3.3 series becoming STABLE the 3.2 series is
  now officially deprecated.

Squid-3.3 represents the first Squid series fully formed within our
rapid release cycle. As such the difference between 3.3 and 3.2 series
is very small and this release of 3.3 constitutes a drop-in replacement
for Squid-3.2.8 with the additional benefit of several SSL-bump
enhancement features only affecting installations using the SSL-bump
features.

This release is a bug fix release resolving:
* a few bugs found when building in MacOSX, Solaris, and OpenIndiana.
* a regression sending authentication credentials to cache_peer

The major changes to be aware of are all from 3.2 bug fixes:

* Fixed several major crashes when opening server connections

These issues affected upstream connections when the client aborted
early or timed out waiting for the final stages of HTTP transaction to
complete.

The messages noting orphan connections are also silenced.

* Cache object size options have been redesigned

In previous versions the interaction of maximum_object_size,
maximum_object_size_in_memory, and cache_dir max-size=N options was
a little confusing and in some configurations would incorrectly cause
objects not to cache at all.

The parameters for maximum stored object size limits in Squid are:

- cache_dir max-size=N options are the authoritive setting for what
   size may be stored in that cache directory.
- the maximum_object_size directive is only the default value for
   any cache_dir where max-size= parameter is not set explicitly.
- maximum_object_size_in_memory is the equivalent to a max-size=N
   option for the cache_mem RAM cache.
- maximum object size cached by Squid is the size of the largest
   size limit from any cache_dir or memory cache.

No configuration changes are required to take advantage of this update.
However, the caching behaviour of some configurations may alter visibly.

* All Squid-2.7 directives are now accepted by Squid-3.

Previously leaving a number of Squid-2.7 directives in squid.conf
would cause Squid-3 to halt on startup citing Bungled squid.conf.

 From this release all directive names supported by Squid-2.7 and 2.6
are accepted by the Squid-3. This does not mean their features are
supported, just that the squid.conf from most Squid-2.7 installations
can be used to start a Squid-3 without encountering Bungled errors.

Running squid -k parse before starting Squid after any upgrade is still
the recommended process. It will highlight any issues that need manual
attention.

The outstanding list of Squid-2.7 features still missing from Squid-3
can be found in the release notes.

* tcp_outgoing_tos bug fixes

The tcp_outgoing_tos directive was not being used correctly on CONNECT
tunnels and the _tos and _mark directives were not using X-Forwarded-For
indirect client IP correctly in their ACL tests.
These isues are now fully resolved.

* Various bugs in diskd and rock storage types

Rock DB cache was being cleared if squid -z was run over an existing and
perfectly valid cache.
The operation of -z is that it will create (only) a directory structure if
missing, or in the case of UFS any missing parts of the whole structure.
It will not validate nor repair other types of damage.

The SHM buffer regression on caches using diskd is fixed.

If you are encountering any of these SHM messages in 3.2.7 (only) they are
a sign of disk files not being closed properly.

* cache_peer persistent connections upgrade

In previous Squid the persistent connections to cache_peer servers has not
been very efficient, to the point that on some peers the keep-alive feature
of HTTP was not working at all.

This release contains a small redesign on the persistent connection re-use
decisions which greatl reduces the FD required for upstream peers and
allows those connections to make full use of keep-alive.
No configuration changes are required to take advantage of this update.

  See the ChangeLog for the full list of changes in this and earlier
  releases.

  All users of older Squid are encouraged to upgrade to this release as
  soon as convenient.

Please remember to run "squid -k parse" when testing upgrade to a new
version of Squid. It will audit your configuration files and report
any identifiable issues the new release will have in your installation
before you "press go". We are still removing the infamous "Bungled
Config" halting points and adding checks, so if something is not
identified please report it.

Please refer to the release notes at
http://www.squid-cache.org/Versions/v3/3.3/RELEASENOTES.html
when you are ready to make the switch to Squid-3.3

Upgrade tip:
   "squid -k parse" is starting to display even more
    useful hints about squid.conf changes.

This new release can be downloaded from our HTTP or FTP servers

http://www.squid-cache.org/Versions/v3/3.3/
ftp://ftp.squid-cache.org/pub/squid/
ftp://ftp.squid-cache.org/pub/archive/3.3/

or the mirrors. For a list of mirror sites see

http://www.squid-cache.org/Download/http-mirrors.html
http://www.squid-cache.org/Download/mirrors.html

If you encounter any issues with this release please file a bug report.
http://bugs.squid-cache.org/

Amos Jeffries
Received on Sat Mar 02 2013 - 10:34:14 MST