-The Squid Team are pleased to announce the release of Squid-3.0.STABLE3.
-
-This new release is available for download from
-Although this release is deemed good enough for use in many setups, please note the existence of
-The 3.0 change history can be
-Squid 3.0 represents a major rewrite of Squid and has a number of new features.
-
-The most important of these are:
-
- 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:
-
- 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 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
-Some of the features found in Squid-2.6 is not available in Squid-3.
-Some have been dropped as they are not needed. Some have 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
-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:
-
-
-
-
-
-