The Squid Team are pleased to announce the release of Squid-@PACKAGE_VERSION@ for testing.
This new release is available for download from http://www.squid-cache.org/Versions/v7/ or the mirrors.
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 https://wiki.squid-cache.org/SquidFaq/BugReporting for how to submit a 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-7.
The Squid-7 change history can be viewed here.
Squid-7 represents a new feature release above Squid-6.
The most important of these new features are:
Most user-facing changes are reflected in squid.conf (see further below).
For more information about the Cache Manager feature, see wiki.
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.
Popular command-line tools such as curl or wget provide equivalent features.
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.
This custom scheme does not conform to RFC 3986 URI sytax. It has been replaced with Cache Manager access through HTTP and HTTPS URLs.
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).
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.
Old Squid used full language name to refer to error page translations. These have been deprecated since addition of ISO-639 language codes and support for HTTP Accept-Language negotiation in Squid-3.x.
As of this release Squid will no longer provide the symlinks needed for seamless upgrade for squid.conf containing settings such as
error_directory English
All Squid installations are expected to already have them,
or to convert to the ISO-639 equivalents. Existing symlinks are not
affected.
See http://www.squid-cache.org/Versions/langpack/ for the latest list of official Squid translations.
See https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes for the full ISO-639 list. HTTP uses the 2-letter (set 1) codes.
This section gives an account of those changes in three categories:
No new directives in this version.
Changed src to detect and handle overlapping IP and IP-range values. Merging where necessary.
Changed dst to detect and handle overlapping IP and IP-range values. Merging where necessary.
Changed localip to detect and handle overlapping IP and IP-range values. Merging where necessary.
Changed ssl::server_name to detect and handle overlapping sub-domain and wildcard domains. Merging or ignoring where necessary.
Changed srcdomain to detect and handle overlapping sub-domain and wildcard domains. Merging or ignoring where necessary.
Changed dstdomain to detect and handle overlapping sub-domain and wildcard domains. Merging or ignoring where necessary.
Changed http_status to detect and handle overlapping status and status-range values. Merging where necessary.
Honor the off setting in 'udp' access_log module.
Removed the non_peers action. See the Cache Manager section for details.
The corresponding code has not built for many years, indicating that the feature is unused.
The corresponding code has not built for many years, indicating that the feature is unused.
The corresponding code has not built for many years, indicating that the feature is unused.
The corresponding code has not built for many years, indicating that the feature is unused.
This section gives an account of those changes in three categories:
Renamed from --without-gnugss.
Disable auto-detection of Windows PSAPI library.
Disable auto-detection of Cyrus SASL (or compatible) library.
Control the listening sockets responsiveness with poll(2) and select(2). The higher the INCOMING_FACTOR, the slower the algorithm will respond to load spikes/increases/decreases in demand. A value between 3 and 8 is recommended. Default is 5.
The ESI feature is now disabled by default. Use --enable-esi if needed.
The cachemgr.cgi tool this option relates to has been removed.
Renamed to --without-gss.
The code enabled by this preprocessor macro has not built for many years, indicating that the feature is unused.
The code enabled by this preprocessor macro has not built for many years, indicating that the feature is unused.
Copyright (C) 1996-2023 The Squid Software Foundation and contributors
Squid software is distributed under GPLv2+ license and includes contributions from numerous individuals and organizations. Please see the COPYING and CONTRIBUTORS files for details.