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

This release is a bug fix release resolving several issues
found in the prior Squid-5 releases and confirming stability
of major functionality changes added in 5.4.1 beta release.

The major changes to be aware of:

 * Bug 5177: clientca certificates sent to https_port clients

A bug in the OpenSSL library has been causing CA certificates
in the Squid tls-clientca= (and previously clientca=) option
be added to the chain of intermediate CA's sent with TLS
server certificate.

This release makes use of an OpenSSL context mode which has
been made available with libssl 1.x to resolve that problem.

Your proxy configuration can be quickly checked for relevance
with the following command:

  squid -k parse 2>&1 | grep clientca

Admin using (tls-)clientca= option should ensure that file
only contains CA to validate the TLS certificates presented
by clients.

To be sent in the TLS handshake Intermediate CA certificates
relevant to the TLS server certificate should be listed in
the file(s) loaded by tls-cert=, tls-cafile= or tls-capath=

 * Bug 5090: Must(!request->pinnedConnection()) violation

This bug is most often seen when ICAP RESPMOD is used, but is
not related to ICAP at all. Visible bug symptoms, if any, may

  FATAL: check failed: !request->pinnedConnection()
  exception location: connectStart

  FATAL: check failed: transportWait
  exception location: noteDestinationsEnd

The bug was actually incorrect handling of servers or peers
whose selection takes unusually long times.

 * Kid restart leads to persistent queue overflows, delays/timeouts

This bug appears in cache.log as any of the following messages:

  WARNING: communication with ... may be too slow or disrupted...
  WARNING: abandoning ... I/Os
  ERROR: worker I/O push queue for ... overflow...
  ERROR: Collapsed forwarding queue overflow...

When one of the SMP worker processes ('kid') crashes or otherwise
exits without cleaning up the SMP memory it was using, the worker
process started to replace it has to automatically recover from
memory corruption. Previous Squid releases did not recover well
from at least the above listed types of corruption.

This release greatly strengthens the recovery process making
Squid much more robust after a worker crash.

 * Bug 5192: esi_parser default is incorrect

This bug appears when Squid is built with both libexpat and
libxml2 available. Updates in Squid-4 unintentionally altered
the default selected to libexpat. This release returns the
default to libxml2 as documented in squid.conf.

  All users of Squid-5 are encouraged to upgrade as soon as

  Users of Squid-4 holding back due to earlier release issues
  are encouraged to test this version for upgrade.

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

Please refer to the release notes at
when you are ready to make the switch to Squid-5

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

or the mirrors. For a list of mirror sites see

If you encounter any issues with this release please file a bug

Amos Jeffries
squid-announce mailing list

Reply via email to