The Squid Team are pleased to announce the release of Squid-3.0.RC1 for pre-release testing.
This new release is available for download from http://www.squid-cache.org/Versions/v3/3.0/ or the mirrors.
A large number of the show-stopper bugs have been fixed along with general improvements to the ICAP support. 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 http://wiki.squid-cache.org/SquidFaq/TroubleShooting#head-7067fc0034ce967e67911becaabb8c95a34d576d for how to submit a report with a stack trace.
Although this release is deemed good enough for testing in many setups, please note the existence of open bugs against Squid-3.0.
The 3.0 change history can be viewed here.
Squid 3.0 represents a major rewrite of Squid and has a number of new features.
The most important of these are:
Most user-facing changes are reflected in squid.conf (see below).
Squid 3.0 supports ICAP/1.0. To enable ICAP support, use the --enable-icap-client ./configure option and icap_enable squid.conf option. You will also need to configure ICAP services in your squid.conf using icap_service, icap_class, and icap_access options. The following example instructs Squid to talk to two ICAP services, one for request and one for response adaptation:
icap_enable on icap_service service_req reqmod_precache 1 icap://127.0.0.1:1344/request icap_service service_resp respmod_precache 0 icap://127.0.0.1:1344/response icap_class class_req service_req icap_class class_resp service_resp icap_access class_req allow all icap_access class_resp allow all
Please see squid.conf.default for more details about these and many other icap_* options.
Squid supports pre-cache request and pre-cache response vectoring points. The following ICAP features are supported: message preview, 204 responses outside of preview, request satisfaction, X-Transfer-* negotiation, persistent ICAP connections, client IP/credentials sharing, and optional bypass of certain service failures.
No more than one ICAP service can be applied to an HTTP message. In other words, chaining or load balancing multiple services is not yet supported.
Proxy-directed data trickling and patience pages are not supported yet.
Following ICAP requirements, Squid never performs HTTP message adaptation without a successful and fresh ICAP OPTIONS response on file. A REQMOD or RESPMOD request will not be sent to a configured ICAP service until Squid receives a valid OPTIONS response from that service. If a service malfunctions or goes down, Squid may stop talking to the service for a while. Several squid.conf options can be used to tune the failure bypass algorithm (e.g., icap_service_failure_limit and icap_service_revival_delay).
The bypass parameter of the icap_service squid.conf option determines whether Squid will try to bypass service failures. Most connectivity and preview-stage failures can be bypassed.
More information about ICAP can be found from the ICAP-forum website http://www.icap-forum.org
ESI is an open specification of an markup language enabling reverse proxies to perform some simple XML based processing, offloading the final page assembly from the webserver and similar tasks.
More information about ESI can be found from the ESI website http://www.esi.org
Some of the features found in Squid-2.6 is not available in Squid-3. Some has been dropped as they are not needed. Some has not yet been forward-ported to Squid-3 and may appear in a later release.
The TCP_REFRESH_HIT and TCP_REFRESH_MISS log types have been replaced because they were misleading (all refreshes need to query the origin server, so they could never be hits). The following log types have been introduced to replace them:
The requested object was cached but STALE. The IMS query for the object resulted in "304 not modified".
The requested object was cached but STALE. The IMS query returned the new content.
See http://www.squid-cache.org/Doc/FAQ/FAQ-6.html#ss6.7 for a definition of all log types.
There have been many changes to Squid's configuration file since Squid-2.6.
This section gives a thorough account of those changes in three categories:
Default: 5
Normally the ICP query timeout is determined dynamically. But
sometimes it can lead to very small timeouts, even lower than
the normal latency variance on your link due to traffic.
Use this option to put an lower limit on the dynamic timeout
value. Do NOT use this option to always use a fixed (instead
of a dynamic) timeout value. To set a fixed timeout see the
'icp_query_timeout' directive.
Default: 10 seconds
Controls how often the ICP pings are sent to siblings that
have background-ping set.
Default: unset
Surrogates (http://www.esi.org/architecture_spec_1.0.html)
need an identification token to allow control targeting. Because
a farm of surrogates may all perform the same tasks, they may share
an identification token.
Default: off
Remote surrogates (such as those in a CDN) honour Surrogate-Control: no-store-remote.
Set this to on to have squid behave as a remote surrogate.
Default: custom
ESI markup is not strictly XML compatible. The custom ESI parser
will give higher performance, but cannot handle non ASCII character
encodings.
Default: on
If enabled, information about the occurred error will be
included in the mailto links of the ERR pages (if %W is set)
so that the email body contains the data.
Syntax is <A HREF="mailto:%w%W">%w</A>
Default: off
When you enable this option, squid will always check
the origin server for an update when a client sends an
If-Modified-Since request. Many browsers use IMS
requests when the user requests a reload, and this
ensures those clients receive the latest version.
By default (off), squid may return a Not Modified response
based on the age of the cached version.
Replaces the header_access directive of Squid-2.6 and earlier, but applies to requests only.
Replaces the header_access directive of Squid-2.6 and earlier, but applies to replies only.
Default: off
If you want to enable the ICAP module support, set this to on.
Default: off
Set this to 'on' if you want to enable the ICAP preview
feature in Squid.
Default: -1
The default size of preview data to be sent to the ICAP server.
-1 means no preview. This value might be overwritten on a per server
basis by OPTIONS requests.
Default: 60
The default TTL value for ICAP OPTIONS responses that don't have
an Options-TTL header.
Default: on
Whether or not Squid should use persistent connections to
an ICAP server.
Default: off
This adds the header "X-Client-IP" to ICAP requests.
Default: off
This adds the header "X-Client-Username" to ICAP requests
if proxy access is authentified.
Default: none
Defines a single ICAP service
icap_service servicename vectoring_point bypass service_url
vectoring_point = reqmod_precache|reqmod_postcache|respmod_precache|respmod_postcache
This specifies at which point of request processing the ICAP
service should be plugged in.
bypass = 1|0
If set to 1 and the ICAP server cannot be reached, the request will go
through without being processed by an ICAP server
service_url = icap://servername:port/service
Note: reqmod_precache and respmod_postcache is not yet implemented
Example:
icap_service service_1 reqmod_precache 0 icap://icap1.mydomain.net:1344/reqmod
icap_service service_2 respmod_precache 0 icap://icap2.mydomain.net:1344/respmod
Default: none
Defines an ICAP service chain. If there are multiple services per
vectoring point, they are processed in the specified order.
icap_class classname servicename...
Example:
icap_class class_1 service_1 service_2
icap class class_2 service_1 service_3
Default: none
Redirects a request through an ICAP service class, depending
on given acls
icap_access classname allow|deny [!]aclname...
The icap_access statements are processed in the order they appear in
this configuration file. If an access list matches, the processing stops.
For an "allow" rule, the specified class is used for the request. A "deny"
rule simply stops processing without using the class. You can also use the
special classname "None".
For backward compatibility, it is also possible to use services
directly here.
Example:
icap_access class_1 allow all
The name of an accept(2) filter to install on Squid's
listen socket(s). This feature is perhaps specific to
FreeBSD and requires support in the kernel.
The 'httpready' filter delays delivering new connections
to Squid until a full HTTP request has been received.
See the accf_http(9) man page.
New options:
disable-pmtu-discovery=
Control Path-MTU discovery usage:
off lets OS decide on what to do (default).
transparent disable PMTU discovery when transparent support is enabled.
always disable always PMTU discovery.
In many setups of transparently intercepting proxies Path-MTU
discovery can not work on traffic towards the clients. This is
the case when the intercepting device does not fully track
connections and fails to forward ICMP must fragment messages
to the cache server. If you have such setup and experience that
certain clients sporadically hang or never complete requests set
disable-pmtu-discovery option to 'transparent'.
Removed options:
urlgroup=, not yet ported to Squid-3.
no-connection-auth, not yet ported to Squid-3.
Removed options:
urlgroup=, not yet ported to Squid-3.
New options:
basetime=n
background-ping
weighted-round-robin
use 'basetime=n' to specify a base amount to
be subtracted from round trip times of parents.
It is subtracted before division by weight in calculating
which parent to fectch from. If the rtt is less than the
base time the rtt is set to a minimal value.
use 'background-ping' to only send ICP queries to this
neighbor infrequently. This is used to keep the neighbor
round trip time updated and is usually used in
conjunction with weighted-round-robin.
use 'weighted-round-robin' to define a set of parents
which should be used in a round-robin fashion with the
frequency of each parent being based on the round trip
time. Closer parents are used more often.
Usually used for background-ping parents.
Removed options:
userhash, not yet ported to Squid-3
sourcehash, not yet ported to Squid-2
monitorurl, monitorsize etc, not yet ported to Squid-3
connection-auth=, not yet ported to Squid-3
Common options
no-store, replaces the older read-only option
min-size, not yet portedto Squid-3
COSS file system:
The coss file store is experimental, and still lacks much
of the functionality found in 2.6.
overwrite-percent=n, not yet ported to Squid-3.
max-stripe-waste=n, not yet ported to Squid-3.
membufs=n, not yet ported to Squid-3.
maxfullbufs=n, not yet ported to Squid-3.
Removed Basic auth option
blankpasswor, not yet ported to squid-3.
auth_param basic concurrency 0
Removed digest options:
concurrency, not yet ported to Squid-3.
New format specifications:
%URI Requested URI
%PATH Requested URL path
Removed format specifications:
%ACL, not yet ported to Squid-3
%DATA, not yet ported to Squid-3
New result keywords:
tag= Apply a tag to a request (for both ERR and OK results)
Only sets a tag, does not alter existing tags.
New options:
ignore-no-store
refresh-ims
ignore-no-store ignores any ``Cache-control: no-store''
headers received from a server. Doing this VIOLATES
the HTTP standard. Enabling this feature could make you
liable for problems which it causes.
refresh-ims causes squid to contact the origin server
when a client issues an If-Modified-Since request. This
ensures that the client will receive an updated version
if one is available.
New types:
acl aclname http_status 200 301 500- 400-403 ... # status code in reply
Removed types:
acl aclname urllogin [-i] [^a-zA-Z0-9] ... # regex matching on URL login field
acl urlgroup group1 ...
# match against the urlgroup as indicated by redirectors
New default:
Default: on
(Old default: off)
New delay classes:
class 4 Everything in a class 3 delay pool, with an
additional limit on a per user basis. This
only takes effect if the username is established
in advance - by forcing authentication in your
http_access rules.
class 5 Requests are grouped according their tag (see
external_acl's tag= reply).
New default to require the feature to be enabled in squid.conf:
Default: 0 (disabled)
(Old default: 4827)
New default to require the feature to be enabled in squid.conf:
Default: 0 (disabled)
(Old default: 3130)
New default to require the feature to be enabled in squid.conf:
Default: 0 (disabled)
(Old default: 3401)
New format tags:
rp Request URL-Path excluding hostname
et Tag returned by external acl
<sH Reply high offset sent
<sS Upstream object size
Removed format tags:
>st Request size including HTTP headers, not yet ported to Squid-3.
st Request+Reply size including HTTP headers, not yet ported to Squid-3.
Syntax changed:
reply_body_max_size size [acl acl...]
allow/deny no longer used.
No urlgroup support in either requests or responese
Not yet ported to Squid-3.
Not yet ported to Squid-3.
Not yet ported to Squid-3.
Not yet ported to Squid-3.
Not yet ported to Squid-3.
Not yet ported to Squid-3.
This has been replaced by request_header_access and reply_header_access
Not yet ported to Squid-3.
Replaced by disable-pmtu-discovery http_port option
Not yet ported to Squid-3.
Not yet ported to Squid-3.
Not yet ported to Squid-3.
equivalent to cache_peer + cache_peer_access.
There have been some changes to Squid's build configuration since Squid-2.6.
This section gives an account of those changes in three categories:
Build shared libraries. The default is to build without.
Build static libraries. The default is on.
Optimize for fast installation
default: yes
Avoid locking (might break parallel builds)
Don't compile Squid with compiler optimizations enabled. Optimization is good for production builds, but not good for debugging. During development, use --disable-optimizations to reduce compilation times and allow easier debugging. This option implicitly also enables --disable-inline
Don't compile trivial methods as inline. Squid is coded with much of the code able to be inlined. Inlining is good for production builds, but not good for development. During development, use --disable-inline to reduce compilation times and allow incremental builds to be quick. For production builds, or load tests, use --enable-inline to have squid make all trivial methods inlinable by the compiler.
Provide some debug information in cbdata
Build support for the list of disk I/O modules. The default is only to build the "Blocking" module. See src/DiskIO for a list of available modules, or Programmers Guide for details on how to build your custom disk module.
Enable ESI for accelerators. Requires libexpat. Enabling ESI will cause squid to follow the Edge Acceleration Specification (www.esi.org). This causes squid to IGNORE client Cache-Control headers.
DO NOT use this in a squid configured as a web proxy, ONLY use it in a squid configured for webserver acceleration.
Enable the ICAP client.
Disable SNMP monitoring support which is now built by default.
Disable HTCP protocol support which is now built by default.
Enable kqueue() support. Marked as experimental in 3.0.
Enable Transparent Proxy support for systems using FreeBSD IPFW style redirection.
Disable memPools. Note that this option now simply sets the default behaviour. Specific classes can override this at runtime, and only lib/MemPool.c needs to be altered to change the squid-wide default for all classes.
This option allows you to see which internal functions in Squid are consuming how much CPU. Compiles in probes that measure time spent in probed functions. Needs source modifications to add new probes. This is meant for developers to assist in performance optimisations of Squid internal functions.
If you are not developer and not interested in the stats you shouldn't enable this, as overhead added, although small, is still overhead. See lib/Profiler.c for more.
Assume the C compiler uses GNU ld. The default is to auto-detect.
Try to use only PIC/non-PIC objects. The default is to use both.
Include additional configurations. The default is automatic.
Sets the default System User account for squid permissions. The default is 'nobody' as in other releases of squid.
Path where the cppunit headers and libraries are found for unit testing. The default is automatic detection.
NOTE: Since 3.0-PRE6 and 2.6STABLE14 squid no longer comes bundled with CPPUnit. Compile-time validation will be disabled if it is not installed on your system.
CARP support is now built by default. --disable-carp can be used to buidl without it.
HTCP protocol support is now built by default. Use --disable-htcp to build without it.
SNMP monitoring is now build by default. Use --disable-snmp to build without it.
Please use --enable-removal-policies directive instead.
Replaced by --with-filedescriptors=N
Override maximum number of filedescriptors. Useful if you build as another user who is not privileged to use the number of filedescriptors you want the resulting binary to support
Deprecated. Automatic checks will enable best I/O loop method available.
Deprecated. Automatic checks will enable best I/O loop method available.
Deprecated. Automatic checks will enable best I/O loop method available.
kqueue support is marked Experimental in Squid 3.0. Known to have some issues under load.
These configure options have not yet been ported to Squid-3. If you need something to do then porting one of these from Squid-2 to Squid-3 is most welcome.
Support for Solaris /dev/poll
Basic POSIX select() loop without any binary fd_set optimizations.
Support following the X-Forwarded-For HTTP header for determining the client IP address
The following configure options have been removed.
Most OS:es have good malloc implementations these days, and the version we used to ship with Squid was very very old..
Debug option, not needed and therefore removed.
Rarely used extra log file. Removed.
Rarely used feature, and multicast ICP acheives almost the same result. Removed.
Specific to the COSS implementation in Squid-2
Now enabled by default. Configure option was redundant and therefore removed.
Known to cause race conditions where cache objects may get corrupted, and this for at most a marginal performance improvement. Removed.