The Squid Team are pleased to announce the release of Squid-@PACKAGE_VERSION@ for testing. This new release is available for download from or the .

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

We welcome feedback and bug reports. If you find a bug, please see for how to submit a report with a stack trace. Known issues

Although this release is deemed good enough for use in many setups, please note the existence of . Changes since earlier releases of Squid-@SQUID_RELEASE@

The Squid-@SQUID_RELEASE@ change history can be . Major new features since Squid-@SQUID_RELEASE_OLD@

Squid-@SQUID_RELEASE@ represents a new feature release above Squid-@SQUID_RELEASE_OLD@.

The most important of these new features are: Cache Manager changes Removed purge tool

Most user-facing changes are reflected in squid.conf (see further below). Cache Manager changes

For more information about the Cache Manager feature, see .

In order to reduce workload on the Squid development team we have chosen to stop providing several tools related to Cache Manager which have previously been bundled with Squid. Removal of the squidclient tool.

Popular command-line tools such as curl or wget provide equivalent features. Removal of the cachemgr.cgi tool.

Access to the Cache Manager API is available by sending HTTP(S) requests directly to Squid with the URL-path prefix /squid-internal-mgr/. A plethora of tools, such as curl, wget, or any web browser, can be used instead of cachemgr.cgi. Removal of the cache_object: URI scheme.

This custom scheme does not conform to RFC 3986 URI sytax. It has been replaced with Cache Manager access through HTTP and HTTPS URLs. Removal of non_peers Report

Squid still ignores unexpected ICP responses but no longer remembers the details that comprised the removed report. The senders of these ICP messages are still reported to cache.log at debugging level 1 (with an exponential backoff). Removed purge tool

The purge tool (also known as squidpurge, and squid-purge) was limited to managing UFS/AUFS/DiskD caches and had problems parsing non-trivial squid.conf files.

The cache contents display and search it provided can be obtained with a script searching the cache manager objects report.

This tool used the custom PURGE HTTP method to remove cache objects. This can be performed directly on any Squid configured to allow the method. Like so: acl PURGE method PURGE http_access allow localhost PURGE Any HTTP client (such as curl) can then be used to evict objects from the cache, for example: curl -XPURGE --proxy http://127.0.0.1:3128 http://url.to/evict/ Alternatively the HTCP CLR mechanism can be used. Changes to squid.conf since Squid-@SQUID_RELEASE_OLD@

This section gives an account of those changes in three categories:

New directives

No new directives in this version. Changes to existing directives

buffered_logs

Honor the off setting in 'udp' access_log module. cachemgr_passwd

Removed the non_peers action. See the Cache Manager for details. Removed directives

mcast_miss_addr

The corresponding code has not built for many years, indicating that the feature is unused. mcast_miss_ttl

The corresponding code has not built for many years, indicating that the feature is unused. mcast_miss_port

The corresponding code has not built for many years, indicating that the feature is unused. mcast_miss_encode_key

The corresponding code has not built for many years, indicating that the feature is unused. Changes to ./configure options since Squid-@SQUID_RELEASE_OLD@

This section gives an account of those changes in three categories: New options

--without-psapi

Disable auto-detection of Windows PSAPI library. Changes to existing options

No changed options in this version.