Special thanks go to people who have volunteered their time, effort,
and ideas to make this software available.
- Adrian Chadd <adrian@creative.net.au>
+ Adam Ciarcinski
+ Adrian Chadd <adrian@squid-cache.org>
+ Alex Rousskov <rousskov@measurement-factory.com>
Alexander B. Demenshin <aldem@barnet.kharkov.ua>
Alexander Lukyanov <lav@yar.ru>
Alexey Veselovsky <alexey.veselovsky@eykontech.com>
- Alex Rousskov <rousskov@measurement-factory.com>
+ Alin Nastac <mrness@gentoo.org>
Alter <alter@alter.org.ua>
Amos Jeffries <squid3@treenet.co.nz>
Andreas Lamprecht <Andreas.Lamprecht@siemens.at>
Andres Kroonmaa <andre@ml.ee>
+ Andrew Hoying <andrew_hoying@blm.gov>
Andrey Shorin <tolsty@tushino.com>
Ansgar Hockmann <Ansgar.Hockmann@hrz.uni-dortmund.de>
Anthony Baxter <arb@connect.com.au>
Arjan de Vet <Arjan.deVet@adv.IAEhv.nl>
+ Arkin <arkin.yang@gmail.com>
Arthur Tumanyan <arthurtumanyan@yahoo.com>
Assar Westerlund <assar@pdc.kth.se>
+ Automatic source maintenance <squidadm@squid-cache.org>
Axel Westerhold <ml.awesterhold@dts.de>
Benno Rice <benno@squid-cache.org>
+ Bertrand Jacquin <beber@meleeweb.net>
Bojan Smojver <bojan@rexursive.com>
Brad Smith <brad@comstyle.com>
+ Brian <hiryuu@envisiongames.net>
Brian Degenhardt <bmd@mp3.com>
Brian Denehy <B-Denehy@adfa.oz.au>
- Brian <hiryuu@envisiongames.net>
Bruce Murphy <pack-squid@rattus.net>
Carson Gaspar (carson@lehman.com, carson@cs.columbia.edu)
+ Chris Hills <chaz@chaz6.com>
Christos Tsantilas <chtsanti@users.sourceforge.net>
+ Cloyce <cloyce.spradling@sun.com>
Constantin Rack
Cord Beermann <cord@cc.fh-lippe.de>
Daniel O'Callaghan <danny@miriworld.its.unimelb.EDU.AU>
David Luyer <luyer@ucs.uwa.edu.au>
+ Diego Woitasen <diegows@xtech.com.ar>
Dmitry Kurochkin
+ Don Hopkins <dhopkins@DonHopkins.com>
Doug Dixon <doug.dixon@gmail.com>
Doug Urner <dlu@bsdi.com>
Dragutin Cirkovic <painkiller@gromnet.net>
Duane Wessels <wessels@squid-cache.org>
+ Dustin J. Mitchell
Ed Knowles <ed@fatboy.geog.unsw.edu.au>
Edward Moy <moy@parc.xerox.com>
Emilio Casbas <ecasbas@unav.es>
Finn Thain <fthain@telegraphics.com.au>
Flavio Pescuma <flavio@marasystems.com>
Francesco Chemolli <kinkie@squid-cache.org>
- Francesco Salvestrini and Dustin J. Mitchell
+ Francesco Salvestrini
Francis Daly <francis@daoine.org>
Francois Cami <fcami@winsoft.fr>
Frank Balluffi
+ Frank Schmirler <squid@schmirler.de>
Geoff Keating <Geoff.Keating@anu.edu.au>
George Michaelson <ggm@connect.com.au>
Georgy Salnikov <sge@nmr.nioch.nsc.ru>
Glenn Chisholm <glenn@ircache.net>
Golub Mikhail
Gonzalo Arana <gonzalo.arana@gmail.com>
- Guido Serassio <guido.serassio@acmeconsulting.it>
+ Graham Keeling <graham@equiinet.com>
+ Guido Serassio <serassio@squid-cache.org>
Hasso Tepper <hasso@estpak.ee>
Henrik Nordstrom <henrik@henriknordstrom.net>
Hide Nagaoka <hide@cc.meisei-u.ac.jp>
Ian Castle <ian.castle@coldcomfortfarm.net>
Ian Turner <vectro@pipeline.com>
Igor Vinokurov <igor@cs.ibank.ru>
+ Isnard <isnardjaquet@gmail.com>
+ JPP <jpp1@frws.com>
+ Jakub Wilk <ubanus@users.sf.net>
+ James Brotchie <brotchie@gmail.com>
James R Grinter <jrg@demon.net>
Jan Niehusmann <jan@anduin.gondor.mcs.de>
Jean-Francois Micouleau <Jean-Francois.Micouleau@utc.fr>
+ Jean-Gabriel Dick <jean-gabriel.dick@curie.fr>
Jerry Murdock <jmurdock@itraktech.com>
Joachim Bauch <jojo@fistofbenztown.de>
+ Joao Alves Neto <alves_joao@hotmail.com>
+ Jochen Voss <voss@seehuhn.de>
Joe Ramey <ramey@jello.csc.ti.com>
John Dilley <jad@hpl.hp.com>
John Saunders <johns@rd.scitec.com.au>
- Jonathan Larmour <JLarmour@origin-at.co.uk>
+ Johnathan Conley <johnathan.conley@gmail.com>
Jon Thackray <jrmt@uk.gdscorp.com>
+ Jonathan Larmour <JLarmour@origin-at.co.uk>
Joshua Root <josh+squid@root.id.au>
- JPP <jpp1@frws.com>
+ Kieran Whitbread <k.j.whitbread@qmul.ac.uk>
Klaubert Herr <klaubert@gmail.com>
Klaus Singvogel <kssingvo@suse.de>
Kolics Bertold <bertold@tohotom.vein.hu>
Kostas Anagnostakis <kanag@csi.forth.gr>
+ Lab10 <lab10@bt-anlagenbau.at>
Laszlo Attilla Toth <panther@balabit.hu>
Leeann Bent <lbent@cs.ucsd.edu>
Luigi Gangitano <luigi@debian.org>
Mark Bergsma <mark@nedworks.org>
Mark Nottingham <mnot@pobox.com>
Mark Treacy <mark@aone.com.au>
+ Marko <mr_4u2@yahoo.com>
Markus Gyger <mgyger@itr.ch>
- Markus <huaraz@moeller.plus.com>
Markus Moeller <huaraz@moeller.plus.com>
- Markus Moeller <markus_moeller@compuserve.com>
Markus Stumpf <maex@Space.NET>
Martin Hamilton <martin@mrrl.lut.ac.uk>
+ Martin Huter <m.huter@phion.com>
Masashi Fujita <objectx@bandit.co.jp>
Massimo Zito <zmax.linkedin at gmail dot com>
Matthew Morgan <atcs.matthew@gmail.com>
+ Matthias Pitzl <silamael@coronamundi.de>
Max Okumoto <okumoto@ucsd.edu>
Michael Lupp <mike@nemesis.saar.de>
Michael Mansour <mic@shell.gnxs.com.au>
Michael O'Reilly <michael@metal.iinet.net.au>
Michael Pelletier <mikep@comshare.com>
+ Michael van Elst
Miguel A.L. Paraz <map@iphil.net>
Mike Groeneweg <mikeg@scorpion.murdoch.edu.au>
Mike Mitchell <Mike.Mitchell@sas.com>
Pedro Ribeiro <pribeiro@isel.pt>
Pete Bentley <pete@demon.net>
Peter Hidas <peter.hidas@safeland.hu>
+ Peter Pramberger <peter@pramberger.at>
+ Philip Allison <philip.allison@smoothwall.net>
+ Philippe Lantin <plantin@cobaltgroup.com>
Pierangelo Masarati <ando@sys-net.it>
Pierre-Louis BRENAC <brenacp@esiee.fr>
Przemek Czerkas <pczerkas@mgmnet.pl>
Rafael Martinez Torres <rmartine@fdi.ucm.es>
+ Rafal Ramocki <maniac@sistbg.net>
+ Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Ralph Loader <loader@maths.ox.ac.uk>
+ Regardt van de Vyver <squid@vdvyver.net>
+ Reinhard Sojka <reinhard.sojka@parlament.gv.at>
+ Rene Geile <rene.geile@t-online.de>
Reuben Farrelly <reuben@reub.net>
Richard Huveneers <Richard.Huveneers@hekkihek.hacom.nl>
Robert Collins <robertc@robertcollins.net>
- Robert Dessa
+ Robert Forster
Rodrigo Campos (rodrigo@geekbunker.org)
Ron Gomes <rrg@ny.ubs.com>
Russell Street <r.street@auckland.ac.nz>
Shigechika Aikawa <shige@luck.imasy.or.jp>
Stephen R. van den Berg <srb@cuci.nl>
Steve Bennett <S.Bennett@lancaster.ac.uk>
+ Steve Snyder <swsnyder@snydernet.net>
Steven Wilton <swilton@q-net.net.au>
Stewart Forster <slf@connect.com.au>
Svenx <svensven@gmail.com>
Taavi Talvik <taavi@uninet.ee>
Taketo Kabe <kabe@shiratori.riec.tohoku.ac.jp>
- Thomas-Martin Seck <tmseck@netcologne.de>
Thomas Ristic <thr@bootet.net>
+ Thomas-Martin Seck <tmseck@netcologne.de>
Tim Starling <tstarling@wikimedia.org>
Tony Lorimer <tlorimer@au.mdis.com>
+ Unknown - NetBSD Project
+ Vincent Regnard
Vitaliy Matytsyn (main) <vm@if.bank.gov.ua>
Wesha <wesha@iname.com>
Wojtek Sylwestrzak <W.Sylwestrzak@icm.edu.pl>
+ Wolfgang Nothdurft <wolfgang@linogate.de>
+ fancyrabbit <fancyrabbit@gmail.com>
+ vollkommen <vollkommen@gmx.net>
+Changes to squid-3.1.1 (29 Mar 2010):
+
+ - Bug 2873: undefined symbol
+ - Bug 2827: assertion in authentication
+ - Remove ufsdump binary from default builds
+ - Remove pinger from default startups
+ - ... and several documentation updates.
+
Changes to squid-3.1.0.18 (14 Mar 2010):
- Regression Fix: IPv4-mapped prefix, broken in 3.1.0.16
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.65">
- <TITLE>Squid 3.1.0.18 release notes</TITLE>
+ <TITLE>Squid 3.1.1 release notes</TITLE>
</HEAD>
<BODY>
-<H1>Squid 3.1.0.18 release notes</H1>
+<H1>Squid 3.1.1 release notes</H1>
<H2>Squid Developers</H2>
<HR>
<HR>
<H2><A NAME="s1">1.</A> <A HREF="#toc1">Notice</A></H2>
-<P>The Squid Team are pleased to announce the release of Squid-3.1.0.18 for testing.</P>
+<P>The Squid Team are pleased to announce the release of Squid-3.1.1.</P>
<P>This new release is available for download from
<A HREF="http://www.squid-cache.org/Versions/v3/3.1/">http://www.squid-cache.org/Versions/v3/3.1/</A> or the
<A HREF="http://www.squid-cache.org/Mirrors/http-mirrors.html">mirrors</A>.</P>
<P>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.</P>
-<P>We welcome feedback and bug reports. If you find a bug, please see
-<A HREF="http://wiki.squid-cache.org/SquidFaq/TroubleShooting#head-7067fc0034ce967e67911becaabb8c95a34d576d">http://wiki.squid-cache.org/SquidFaq/TroubleShooting#head-7067fc0034ce967e67911becaabb8c95a34d576d</A> for how to submit a report with a stack trace.</P>
+While this release is not fully bug-free we believe it is ready for use in production on many systems.</P>
+<P>We welcome feedback and bug reports. If you find a new bug, please see
+<A HREF="http://wiki.squid-cache.org/SquidFaq/BugReporting">http://wiki.squid-cache.org/SquidFaq/BugReporting</A> for how to submit a report with a stack trace and other required details. Additional information is also very welcome on other open bugs.</P>
<H2><A NAME="ss1.1">1.1</A> <A HREF="#toc1.1">Known issues</A>
</H2>
<P>Although this release is deemed good enough for use in many setups, please note the existence of
-<A HREF="http://www.squid-cache.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&target_milestone=3.1&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=bugs.bug_severity&field0-0-0=noop&type0-0-0=noop&value0-0-0=">open bugs against Squid-3.1</A>.</P>
+<A HREF="http://bugs.squid-cache.org/buglist.cgi?query_format=advanced&target_milestone=3.1&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=bugs.bug_severity">open bugs against Squid-3.1</A>.</P>
+
+<P>Some issues to note as currently known in this release which are not able to be fixed in this 3.1 series are:</P>
+<P>
+<UL>
+<LI>The lack of some features available in Squid-2.x series. See the regression sections below for full details.</LI>
+<LI>The lack of IPv6 split-stack support for MacOSX, OpenBSD and maybe others.</LI>
+</UL>
+</P>
+
+<P>Currently known issues which only depends on available developer time and may still be resolved in a future 3.1 release are:</P>
+<P>
+<UL>
+<LI>IPv4 fall-back occasionally failing on dual IPv4/IPv6 websites.</LI>
+<LI>An ongoing slow FD leak introduced somewhere during the Squid-3.0 cycle.</LI>
+<LI>Windows support is still largely missing.</LI>
+<LI>Build status for the 3.x series is still largely unknown for Unix based OS and other less popular systems.</LI>
+</UL>
+</P>
+
<H2><A NAME="ss1.2">1.2</A> <A HREF="#toc1.2">Changes since earlier releases of Squid-3.1</A>
</H2>
<H2><A NAME="ss2.1">2.1</A> <A HREF="#toc2.1">New Version Numbering System</A>
</H2>
-<P>Begining with 3.1 the Squid Developers are trialling a new release numbering system.</P>
+<P>Begining with 3.1 the Squid Developers are using a new release numbering system.</P>
<P>We have decided, based on input from interested users to drop the Squid-2 terminology of
(DEVEL, PRE, RC, and STABLE) from the release package names.
<P>squid.conf has undergone a facelift.</P>
<P>Don't worry, few operational changes have been made.
-Older configs from are still expected to run in 3.1 with only the usual minor
+Older configs from Squdi 2.x and 3.0 are still expected to run in 3.1 with only the usual minor
changes seen between major release. Details on those are listed below.</P>
-<P>New users will be relieved to see a short 32-line or less squid.conf on clean installs.
+<P>New users will be relieved to see a very short squid.conf on clean installs.
Many of the options have reasonable defaults but had previously needed them explicitly configured!
These are now proper built-in defaults and no longer need to be in squid.conf unless changed.</P>
<P>All of the option documentation has been offloaded to another file <EM>squid.conf.documented</EM> which
-contains a fully documented set of options previously cluttering up squid.conf itself.</P>
+contains a fully documented set of available options previously cluttering up squid.conf itself.</P>
<P>Package maintainers are provided with a second file squid.conf.default which as always contains the default
config options provided on a clean install.</P>
+<P>We are also providing online copies of configuration documentation.
+Updated live to match the latest release of each Squid series, and a combined global version.
+This is available on
+<A HREF="http://www.squid-cache.org/Doc/config/">the Squid website</A></P>
+
<H2><A NAME="ss2.3">2.3</A> <A HREF="#toc2.3">Internet Protocol version 6 (IPv6)</A>
</H2>
<P>Pinger has been upgraded to perform both ICMP and ICMPv6 as required.
As a result of this and due to a change in the binary protocol format between them,
-new builds of squid are no longer backwards-compatible with old pinger binaries.
-You will need to perform "make install-pinger" again after installing squid.</P>
+new builds of Squid are no longer backwards-compatible with old pinger binaries.
+You will need to perform "make install-pinger" again after installing Squid.</P>
<P>Peer and Client SNMP tables have been altered to handle IPv6 addresses.
As a side effect of this the long-missing fix to show seperate named peers on one IP
has been integrated. Making the SNMP peer table now produce correct output.
The table structure change is identical for both IPv4-only and Dual modes but with
IPv4-only simply not including any IPv6 entries. This means any third-party SNMP
-software which hard coded the MIB paths needs to be upgraded for this Squid release.</P>
-
+software which hard coded the MIB paths needs to be upgraded for this Squid release.
+Details can be found in the wiki
+<A HREF="http://wiki.squid-cache.org/Features/Snmp#Squid_OIDs">SNMP feature page</A>.</P>
<H3>Limitations of IPv6 Support</H3>
+<P>In this release there is no split-stack support. This means that OS which do not provide
+IP stacks based on the KAME stack with Hybrid extensions to do IPv4-mapping cannot use IPv6
+with Squid.</P>
+
<P>Specify a specific tcp_outgoing_address and the clients who match its ACL are limited
to the IPv4 or IPv6 network that address belongs to. They are not permitted over the
IPv4-IPv6 boundary. Some ACL voodoo can however be applied to explicitly route the
<P>WCCP is not available (neither version 1 or 2).
It remains built into squid for use with IPv4 traffic but IPv6 cannot use it.</P>
-<P>Transparent Interception is done via NAT at the OS level and is not available in IPv6.
-Squid will ensure that any port set with transparent, intercept, or tproxy options be an IPv4-only
+<P>Pseudo-Transparent Interception is done via NAT at the OS level and is not available in IPv6.
+Squid will ensure that any port set with transparent or intercept options be an IPv4-only
listening address. Wildcard can still be used but will not open as an IPv6.
To ensure that squid can accept IPv6 traffic on its default port, an alternative should
be chosen to handle transparently intercepted traffic.
</PRE>
</P>
+<P>Real transparent Interception (TPROXY) may be able to perform IPv6 interception.
+However this currently still needs kernel patching with experimental patches to enable IPv6.
+Squid will attempt to discover support on startup and may permit or deny IPv6 wildcard for
+tproxy flagged ports depending on your system.</P>
+
<P>The bundled NTLM Auth helper is IPv4-native between itself and the NTLM server.
A new one will be needed for IPv6 traffic between the helper and server.</P>
<P>For best coverage of languages, using the latest language pack of error files is recommended.
Updates can be downloaded from
-<A HREF="http://www.squid-cahch.org/Versions/langpack/">www.squid-cache.org/Versions/langpack/</A></P>
+<A HREF="http://www.squid-cache.org/Versions/langpack/">www.squid-cache.org/Versions/langpack/</A></P>
<P>The squid developers are interested in making squid available in a wide variety of languages.
Contribution of new languages is encouraged.</P>
<H3>Squid Configuration</H3>
-<P>Squid 3.1 needs to be configured with --enable-zph-qos for the ZPH QoS controls to be available.</P>
+<P>Squid 3.1 needs to be configured with <EM>--enable-zph-qos</EM> for the ZPH QoS controls to be available.</P>
-<P>The configuration options for 2.7 and 3.1 are based on different ZPH patches.
+<P>The configuration options for Squid 2.7 and 3.1 are based on different ZPH patches.
The two releases configuration differs and only the TOS mode settings are directly translatable.</P>
<P>
<UL>
</UL>
</P>
-<P>The lines above are spearated for documentation. qos_flows may be configured with all options on one line, or separated as shown.
+<P>The lines above are separated for documentation. qos_flows may be configured with all options on one line, or separated as shown.
Also options may be repeated as many times as desired. Only the final configured value for any option will be used.</P>
<P>The legacy <EM>Option</EM> and <EM>Priority</EM> modes available in Squid-2.7 are no longer supported.</P>
<P>Details in
<A HREF="http://wiki.squid-cache.org/Features/SslBump">The Squid wiki</A></P>
-<P>Squid-in-the-middle decryption and encryption of straight CONNECT and transparently redirected SSL traffic,
+<P>Squid-in-the-middle decryption and encryption of CONNECT tunneled SSL traffic,
using configurable client- and server-side certificates.
While decrypted, the traffic can be inspected using ICAP.</P>
+<P>Squid 3.1 releases limit SSL Bump to CONNECT requests and requires that clients are
+configured to explicitly use the proxy in their browser settings or via WPAD/PAC
+configuration. Use of interception for port 443 is not officially supported, despite
+being known to work under certain limited networking circumstances.</P>
+
<H2><A NAME="ss2.8">2.8</A> <A HREF="#toc2.8">eCAP Adaptation Module support</A>
</H2>
<P>Details in
<A HREF="http://wiki.squid-cache.org/Features/eCAP">The Squid wiki</A></P>
+<P>eCAP provides a way to integrate CAP modules directly into Squid without the need for
+a c-icap server wrapper. This enables faster processing.</P>
+
+<P>Currently known and available eCAP modules are listed in the wiki feature page on eCAP.</P>
+
+
<H2><A NAME="ss2.9">2.9</A> <A HREF="#toc2.9">ICAP Bypass and Retry enhancements</A>
</H2>
should be large enough to not require an explicit configuration in most
environments yet may be small enough to limit side-effects of loops.</P>
+
<H2><A NAME="ss2.10">2.10</A> <A HREF="#toc2.10">ICY streaming protocol support</A>
</H2>
-<P>Squid-3.1 adds native support for streaming protocol ICY.</P>
+<P>Squid-3.1 adds native support for streaming protocol ICY.
+Also commonly known as SHOUTcast multimedia streams.</P>
<P>This protocol uses port 80 and violates RFC 2616 by using an HTTP/1.1 compliant request and non-HTTP reply
to start the stream transaction. If the reply is handled according to HTTP/1.1 RFC-compliance requirements
<P>Squid-2 contained a hack using the <EM>update_http0.9</EM> squid.conf option to work around the
unusual replies. This option is now obsolete.</P>
-<P>The proto ACL type matches <EM>ICY</EM> once the reply has been received, before that the processing
+<P>The <EM>proto</EM> ACL type matches <EM>ICY</EM> once the reply has been received, before that the processing
is only aware on an HTTP request. So the ACL will match <EM>HTTP</EM>.</P>
<PRE>
Control whether the pinger is active at run-time.
Enables turning ICMP pinger on and off with a simple squid -k reconfigure.
- default is on when --enable-icmp is compiled in.
+ default is off when --enable-icmp is compiled in.
</PRE>
</P>
is never forced or permitted out the IPv4 interface.
acl to_ipv6 dst ipv6
+ http_access allow to_ipv6 !all
+
tcp_outgoing_address 2002::c001 good_service_net to_ipv6
tcp_outgoing_address 10.0.0.2 good_service_net !to_ipv6
<P>Build without support for loadable modules.</P>
<DT><B>--disable-strict-error-checking</B><DD>
-<P>Build Squid without advanced compiler error checking.
+<P>Build Squid without advanced compiler error checking (without the -Werror option).
This only affects the building process, enabling it to complete despite some
possibly serious issues.
Please do not use lightly, and please report the build issues which make it needed
<DT><B>--disable-translation</B><DD>
<P>Prevent Squid generating localized error page templates and manuals.
Which is usually tried, but may not be needed.</P>
-<P>This is a development optimization for building from VCS when localization is
-not needed. Has no effect on pre-translated source bundles.</P>
+<P>This is an optimization for building fast when localization is not needed
+or localization tools are not available.</P>
+<P>A copy of the latest translated files can instead be downloaded from
+<A HREF="http://www.squid-cache.org/Versions/langpack/">http://www.squid-cache.org/Versions/langpack/</A></P>
<DT><B>--with-dns-cname</B><DD>
<P>Enable CNAME recursion within the Internal DNS resolver stub squid uses.
<P>Older REDIRECT and DNAT targets work as before on HTTP ports marked 'intercept'.</P>
<DT><B>--enable-linux-tproxy</B><DD>
-<P>Deprecated. Remains only to support old TPROXY version 2.2 installations.</P>
+<P>Deprecated. Remains only to support old TPROXY version 2.2 installations.
+Scheduled for complete removal in Squid 3.2</P>
<DT><B>--enable-ntlm-auth-helpers</B><DD>
<P>Helper previously built by <EM>SMB</EM> is now built by <EM>smb_lm</EM>.
<DT><B>--disable-internl-dns</B><DD>
<P>Better support for Linux using the external DNS helper.
-The helper will now compile and work with dns_nameservers on more variants of Linux than previously.</P>
+The helper will now compile and work with dns_nameservers on more variants of Linux than previously.
+It is still deprecated however and use of this option should be avoided as much as possible.</P>
<DT><B>--with-aio</B><DD>
<P>Deprecated. POSIX AIO is now auto-detected and enabled.
<DT><B>auth_param</B><DD>
<P><EM>blankpassword</EM> option for basic scheme removed.</P>
+<DT><B>cache_peer</B><DD>
+<P><EM>http11</EM> Obsolete.</P>
+
<DT><B>external_acl_type</B><DD>
<P>Format tag <EM>%{Header}</EM> replaced by <EM>%>{Header}</EM></P>
<P>Format tag <EM>%{Header:member}</EM> replaced by <EM>%>{Header:member}</EM></P>
<DT><B>redirector_bypass</B><DD>
<P>Replaced by <EM>url_rewrite_bypass</EM></P>
+<DT><B>server_http11</B><DD>
+<P>Obsolete.</P>
+
<DT><B>upgrade_http0.9</B><DD>
<P>Obsolete. ICY protocol streaming support added natively.</P>
<DT><B>cache_peer</B><DD>
<P><EM>idle=</EM> not yet ported from 2.7</P>
-<P><EM>http11</EM> not yet ported from 2.7</P>
<P><EM>monitorinterval=</EM> not yet ported from 2.6</P>
<P><EM>monitorsize=</EM> not yet ported from 2.6</P>
<P><EM>monitortimeout=</EM> not yet ported from 2.6</P>
<P>Not yet ported from 2.6</P>
<DT><B>logfile_daemon</B><DD>
-<P>Not yet ported from 2.7</P>
+<P>Not yet ported from 2.7.</P>
<DT><B>logformat</B><DD>
<P><EM>%oa</EM> tag not yet ported from 2.7</P>
<DT><B>refresh_stale_hit</B><DD>
<P>Not yet ported from 2.7</P>
-<DT><B>server_http11</B><DD>
-<P>Not yet ported from 2.7</P>
-
<DT><B>storeurl_access</B><DD>
<P>Not yet ported from 2.7</P>
<!doctype linuxdoc system>
<article>
-<title>Squid 3.1.0.18 release notes</title>
+<title>Squid 3.1.1 release notes</title>
<author>Squid Developers</author>
<abstract>
<sect>Notice
<p>
-The Squid Team are pleased to announce the release of Squid-3.1.0.18 for testing.
+The Squid Team are pleased to announce the release of Squid-3.1.1.
This new release is available for download from <url url="http://www.squid-cache.org/Versions/v3/3.1/"> or the <url url="http://www.squid-cache.org/Mirrors/http-mirrors.html" name="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.
+While this release is not fully bug-free we believe it is ready for use in production on many systems.
-We welcome feedback and bug reports. If you find a bug, please see <url url="http://wiki.squid-cache.org/SquidFaq/TroubleShooting#head-7067fc0034ce967e67911becaabb8c95a34d576d"> for how to submit a report with a stack trace.
+We welcome feedback and bug reports. If you find a new bug, please see <url url="http://wiki.squid-cache.org/SquidFaq/BugReporting"> for how to submit a report with a stack trace and other required details. Additional information is also very welcome on other open bugs.
<sect1>Known issues
<p>
-Although this release is deemed good enough for use in many setups, please note the existence of <url url="http://www.squid-cache.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&target_milestone=3.1&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=bugs.bug_severity&field0-0-0=noop&type0-0-0=noop&value0-0-0=" name="open bugs against Squid-3.1">.
+Although this release is deemed good enough for use in many setups, please note the existence of <url url="http://bugs.squid-cache.org/buglist.cgi?query_format=advanced&target_milestone=3.1&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=bugs.bug_severity" name="open bugs against Squid-3.1">.
+
+<p>Some issues to note as currently known in this release which are not able to be fixed in this 3.1 series are:
+
+<itemize>
+ <item>The lack of some features available in Squid-2.x series. See the regression sections below for full details.
+ <item>The lack of IPv6 split-stack support for MacOSX, OpenBSD and maybe others.
+</itemize>
+
+<p>Currently known issues which only depends on available developer time and may still be resolved in a future 3.1 release are:
+
+<itemize>
+ <item>IPv4 fall-back occasionally failing on dual IPv4/IPv6 websites.
+ <item>An ongoing slow FD leak introduced somewhere during the Squid-3.0 cycle.
+ <item>Windows support is still largely missing.
+ <item>Build status for the 3.x series is still largely unknown for Unix based OS and other less popular systems.
+</itemize>
+
<sect1>Changes since earlier releases of Squid-3.1
<p>
<sect1>New Version Numbering System
-<p>Begining with 3.1 the Squid Developers are trialling a new release numbering system.
+<p>Begining with 3.1 the Squid Developers are using a new release numbering system.
<p>We have decided, based on input from interested users to drop the Squid-2 terminology of
(DEVEL, PRE, RC, and STABLE) from the release package names.
<p>squid.conf has undergone a facelift.
<p>Don't worry, few operational changes have been made.
-Older configs from are still expected to run in 3.1 with only the usual minor
+Older configs from Squdi 2.x and 3.0 are still expected to run in 3.1 with only the usual minor
changes seen between major release. Details on those are listed below.
-<p>New users will be relieved to see a short 32-line or less squid.conf on clean installs.
+<p>New users will be relieved to see a very short squid.conf on clean installs.
Many of the options have reasonable defaults but had previously needed them explicitly configured!
These are now proper built-in defaults and no longer need to be in squid.conf unless changed.
<p>All of the option documentation has been offloaded to another file <em>squid.conf.documented</em> which
-contains a fully documented set of options previously cluttering up squid.conf itself.
+contains a fully documented set of available options previously cluttering up squid.conf itself.
<p>Package maintainers are provided with a second file squid.conf.default which as always contains the default
config options provided on a clean install.
+<p>We are also providing online copies of configuration documentation.
+ Updated live to match the latest release of each Squid series, and a combined global version.
+ This is available on <url url="http://www.squid-cache.org/Doc/config/" name="the Squid website">
+
<sect1>Internet Protocol version 6 (IPv6)
<p>Pinger has been upgraded to perform both ICMP and ICMPv6 as required.
As a result of this and due to a change in the binary protocol format between them,
- new builds of squid are no longer backwards-compatible with old pinger binaries.
- You will need to perform "make install-pinger" again after installing squid.
+ new builds of Squid are no longer backwards-compatible with old pinger binaries.
+ You will need to perform "make install-pinger" again after installing Squid.
<p>Peer and Client SNMP tables have been altered to handle IPv6 addresses.
As a side effect of this the long-missing fix to show seperate named peers on one IP
The table structure change is identical for both IPv4-only and Dual modes but with
IPv4-only simply not including any IPv6 entries. This means any third-party SNMP
software which hard coded the MIB paths needs to be upgraded for this Squid release.
-
+ Details can be found in the wiki <url url="http://wiki.squid-cache.org/Features/Snmp#Squid_OIDs" name="SNMP feature page">.
<sect2>Limitations of IPv6 Support
+<p>In this release there is no split-stack support. This means that OS which do not provide
+ IP stacks based on the KAME stack with Hybrid extensions to do IPv4-mapping cannot use IPv6
+ with Squid.
+
<p>Specify a specific tcp_outgoing_address and the clients who match its ACL are limited
to the IPv4 or IPv6 network that address belongs to. They are not permitted over the
IPv4-IPv6 boundary. Some ACL voodoo can however be applied to explicitly route the
<p>WCCP is not available (neither version 1 or 2).
It remains built into squid for use with IPv4 traffic but IPv6 cannot use it.
-<p>Transparent Interception is done via NAT at the OS level and is not available in IPv6.
- Squid will ensure that any port set with transparent, intercept, or tproxy options be an IPv4-only
+<p>Pseudo-Transparent Interception is done via NAT at the OS level and is not available in IPv6.
+ Squid will ensure that any port set with transparent or intercept options be an IPv4-only
listening address. Wildcard can still be used but will not open as an IPv6.
To ensure that squid can accept IPv6 traffic on its default port, an alternative should
be chosen to handle transparently intercepted traffic.
http_port 8080 intercept
</verb>
+<p>Real transparent Interception (TPROXY) may be able to perform IPv6 interception.
+ However this currently still needs kernel patching with experimental patches to enable IPv6.
+ Squid will attempt to discover support on startup and may permit or deny IPv6 wildcard for
+ tproxy flagged ports depending on your system.
+
<p>The bundled NTLM Auth helper is IPv4-native between itself and the NTLM server.
A new one will be needed for IPv6 traffic between the helper and server.
<p>The error_directory option in squid.conf needs to be removed.
<p>For best coverage of languages, using the latest language pack of error files is recommended.
-Updates can be downloaded from <url url="http://www.squid-cahch.org/Versions/langpack/" name="www.squid-cache.org/Versions/langpack/">
+Updates can be downloaded from <url url="http://www.squid-cache.org/Versions/langpack/" name="www.squid-cache.org/Versions/langpack/">
<p>The squid developers are interested in making squid available in a wide variety of languages.
Contribution of new languages is encouraged.
</itemize>
<sect2>Squid Configuration
-<p>Squid 3.1 needs to be configured with --enable-zph-qos for the ZPH QoS controls to be available.
+<p>Squid 3.1 needs to be configured with <em>--enable-zph-qos</em> for the ZPH QoS controls to be available.
-<p>The configuration options for 2.7 and 3.1 are based on different ZPH patches.
-The two releases configuration differs and only the TOS mode settings are directly translatable.
+<p>The configuration options for Squid 2.7 and 3.1 are based on different ZPH patches.
+ The two releases configuration differs and only the TOS mode settings are directly translatable.
<itemize>
<item><em>qos_flows local-hit=0xff</em> Responses found as a HIT in the local cache
<item><em>qos_flows parent-hit=0xff</em> Responses found as a HIT in a parent peer
</itemize>
-<p>The lines above are spearated for documentation. qos_flows may be configured with all options on one line, or separated as shown.
-Also options may be repeated as many times as desired. Only the final configured value for any option will be used.
+<p>The lines above are separated for documentation. qos_flows may be configured with all options on one line, or separated as shown.
+ Also options may be repeated as many times as desired. Only the final configured value for any option will be used.
<p>The legacy <em>Option</em> and <em>Priority</em> modes available in Squid-2.7 are no longer supported.
<p>Details in <url url="http://wiki.squid-cache.org/Features/SslBump" name="The Squid wiki">
-<p>Squid-in-the-middle decryption and encryption of straight CONNECT and transparently redirected SSL traffic,
-using configurable client- and server-side certificates.
-While decrypted, the traffic can be inspected using ICAP.
+<p>Squid-in-the-middle decryption and encryption of CONNECT tunneled SSL traffic,
+ using configurable client- and server-side certificates.
+ While decrypted, the traffic can be inspected using ICAP.
+
+<p>Squid 3.1 releases limit SSL Bump to CONNECT requests and requires that clients are
+ configured to explicitly use the proxy in their browser settings or via WPAD/PAC
+ configuration. Use of interception for port 443 is not officially supported, despite
+ being known to work under certain limited networking circumstances.
<sect1>eCAP Adaptation Module support
<p>Details in <url url="http://wiki.squid-cache.org/Features/eCAP" name="The Squid wiki">
+<p>eCAP provides a way to integrate CAP modules directly into Squid without the need for
+ a c-icap server wrapper. This enables faster processing.
+
+<p>Currently known and available eCAP modules are listed in the wiki feature page on eCAP.
+
+
<sect1>ICAP Bypass and Retry enhancements
<p>Details in <url url="http://wiki.squid-cache.org/Features/ICAP" name="The Squid wiki">
should be large enough to not require an explicit configuration in most
environments yet may be small enough to limit side-effects of loops.
+
<sect1>ICY streaming protocol support
<p>Squid-3.1 adds native support for streaming protocol ICY.
+ Also commonly known as SHOUTcast multimedia streams.
<p>This protocol uses port 80 and violates RFC 2616 by using an HTTP/1.1 compliant request and non-HTTP reply
to start the stream transaction. If the reply is handled according to HTTP/1.1 RFC-compliance requirements
<p>Squid-2 contained a hack using the <em>update_http0.9</em> squid.conf option to work around the
unusual replies. This option is now obsolete.
-<p>The proto ACL type matches <em>ICY</em> once the reply has been received, before that the processing
+<p>The <em>proto</em> ACL type matches <em>ICY</em> once the reply has been received, before that the processing
is only aware on an HTTP request. So the ACL will match <em>HTTP</em>.
<verb>
Control whether the pinger is active at run-time.
Enables turning ICMP pinger on and off with a simple squid -k reconfigure.
- default is on when --enable-icmp is compiled in.
+ default is off when --enable-icmp is compiled in.
</verb>
<tag>ssl_bump</tag>
is never forced or permitted out the IPv4 interface.
acl to_ipv6 dst ipv6
+ http_access allow to_ipv6 !all
+
tcp_outgoing_address 2002::c001 good_service_net to_ipv6
tcp_outgoing_address 10.0.0.2 good_service_net !to_ipv6
<p>Build without support for loadable modules.
<tag>--disable-strict-error-checking</tag>
- <p>Build Squid without advanced compiler error checking.
+ <p>Build Squid without advanced compiler error checking (without the -Werror option).
This only affects the building process, enabling it to complete despite some
possibly serious issues.
Please do not use lightly, and please report the build issues which make it needed
<tag>--disable-translation</tag>
<p>Prevent Squid generating localized error page templates and manuals.
Which is usually tried, but may not be needed.
- <p>This is a development optimization for building from VCS when localization is
- not needed. Has no effect on pre-translated source bundles.
+ <p>This is an optimization for building fast when localization is not needed
+ or localization tools are not available.
+ <p>A copy of the latest translated files can instead be downloaded from
+<url url="http://www.squid-cache.org/Versions/langpack/" name="http://www.squid-cache.org/Versions/langpack/">
<tag>--with-dns-cname</tag>
<p>Enable CNAME recursion within the Internal DNS resolver stub squid uses.
<tag>--enable-linux-tproxy</tag>
<p>Deprecated. Remains only to support old TPROXY version 2.2 installations.
+ Scheduled for complete removal in Squid 3.2
<tag>--enable-ntlm-auth-helpers</tag>
<p>Helper previously built by <em>SMB</em> is now built by <em>smb_lm</em>.
<tag>--disable-internl-dns</tag>
<p>Better support for Linux using the external DNS helper.
The helper will now compile and work with dns_nameservers on more variants of Linux than previously.
+ It is still deprecated however and use of this option should be avoided as much as possible.
<tag>--with-aio</tag>
<p>Deprecated. POSIX AIO is now auto-detected and enabled.
<tag>auth_param</tag>
<p><em>blankpassword</em> option for basic scheme removed.
+ <tag>cache_peer</tag>
+ <p><em>http11</em> Obsolete.
+
<tag>external_acl_type</tag>
<p>Format tag <em>%{Header}</em> replaced by <em>%>{Header}</em>
<p>Format tag <em>%{Header:member}</em> replaced by <em>%>{Header:member}</em>
<tag>redirector_bypass</tag>
<p>Replaced by <em>url_rewrite_bypass</em>
+ <tag>server_http11</tag>
+ <p>Obsolete.
+
<tag>upgrade_http0.9</tag>
<p>Obsolete. ICY protocol streaming support added natively.
<tag>cache_peer</tag>
<p><em>idle=</em> not yet ported from 2.7
- <p><em>http11</em> not yet ported from 2.7
<p><em>monitorinterval=</em> not yet ported from 2.6
<p><em>monitorsize=</em> not yet ported from 2.6
<p><em>monitortimeout=</em> not yet ported from 2.6
<p>Not yet ported from 2.6
<tag>logfile_daemon</tag>
- <p>Not yet ported from 2.7
+ <p>Not yet ported from 2.7.
<tag>logformat</tag>
<p><em>%oa</em> tag not yet ported from 2.7
<tag>refresh_stale_hit</tag>
<p>Not yet ported from 2.7
- <tag>server_http11</tag>
- <p>Not yet ported from 2.7
-
<tag>storeurl_access</tag>
<p>Not yet ported from 2.7
projects / thirdparty / squid.git / commitdiff
