Squid 2.2

SQUID-2.2 releases:

Release	Date	diff
2.2.PRE1	`Sun Jan 24 05:36:09 UTC 1999`	from 2.1.PATCH2
2.2.PRE2	`Sat Jan 30 06:19:46 UTC 1999`	from 2.2.PRE1
2.2.DEVEL3	`Sun Feb 14 08:39:31 UTC 1999`	from 2.2.PRE2
2.2.DEVEL4	`Fri Apr 09 05:01:19 UTC 1999`	from 2.2.DEVEL3
2.2.STABLE1	`Mon Apr 19 02:08:19 UTC 1999`	from 2.2.DEVEL4
2.2.STABLE2	`Wed Apr 21 06:31:53 UTC 1999`	from 2.2.STABLE1
2.2.STABLE3	`Wed May 19 16:11:09 UTC 1999`	from 2.2.STABLE2
2.2.STABLE4	`Wed Jul 07 02:53:20 UTC 1999`	from 2.2.STABLE3
2.2.STABLE5	`Thu Sep 23 19:03:18 UTC 1999`	from 2.2.STABLE4

Reported Bugs for version 2.2.

Important Changes to this version:

The following configuration options have been removed:
- ident_lookup
- cache_mem_low
- cache_mem_high
- acl snmp_community
- http_anonymizer
- snmp_do_queueing
- snmp_mib_path
- trap_sink
- snmp_trap_community
- snmp_agent_conf
- snmp_acl
- persistent_client_posts
The following configuration options have been added:
- ident_lookup_access
- ident_timeout
- anonymize_headers
- snmp_access
- broken_posts
- prefer_direct
- strip_query_terms
Squid now automatically retries failed requests with 5xx status codes. In particular, this means we support only-if-cached option. Squid sends "Cache-control: only-if-cached" in all requests to siblings. If the sibling does not have the object, it returns 504 (Gateway Timeout) and the originating Squid will fetch the object from a parent, or from the source.
Squid behaves more like a proper daemon now. If you type just 'squid', it backgrounds itself and disassociates from your terminal. Error messages are logged to syslog. Use the -N option to prevent daemon-mode behavior.
A new error code, ERR_SHUTTING_DOWN, was added. This error will be sent for requests received while Squid is in the process of shutting down. You must 'make install' from the top-level directory to install this new error page. All of the different language templates have an English version of this error message.
Added three new error pages for FTP (ERR_FTP_NOT_FOUND, ERR_FTP_UNAVAILABLE, and ERR_FTP_FORBIDDEN) which are just more specific cases of the generic ERR_FTP_FAILURE message.

Preserving your 2.1 Cache:

If you are upgrading from Squid-2.1 to Squid-2.2, then you may experience no cache hits for a while. The reason is that we changed the internal cache key calculations between these two versions. The objects stored by Squid-2.1 have the old key format, but Squid-2.2 looks for the new key format.

In order to get cache hits on your old cached objects, you can apply this patch.

Note that over time the new objects are automatically stored with the new cache key. Thus, this patch becomes sort of obsolete after you use it for a month or so. If you upgrade again after a month, you don't need to apply the patch again.