1 <!doctype linuxdoc system>
3 <title>Squid 3.5.3 release notes</title>
4 <author>Squid Developers</author>
7 This document contains the release notes for version 3.5 of Squid.
8 Squid is a WWW Cache application developed by the National Laboratory
9 for Applied Network Research and members of the Web Caching community.
16 The Squid Team are pleased to announce the release of Squid-3.5.3.
18 This new release is available for download from <url url="http://www.squid-cache.org/Versions/v3/3.5/"> or the
19 <url url="http://www.squid-cache.org/Download/http-mirrors.html" name="mirrors">.
21 <p>Some interesting new features adding system flexibility have been added along with general improvements all around.
22 While this release is not fully bug-free we believe it is ready for use in production on many systems.
24 <p>We welcome feedback and bug reports. If you find a bug, please see <url url="http://wiki.squid-cache.org/SquidFaq/BugReporting">
25 for how to submit a report with a stack trace.
29 Although this release is deemed good enough for use in many setups, please note the existence of
30 <url url="http://bugs.squid-cache.org/buglist.cgi?query_format=advanced&product=Squid&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&version=3.5" name="open bugs against Squid-3.5">.
32 <sect1>Changes since earlier releases of Squid-3.5
34 The 3.5 change history can be <url url="http://www.squid-cache.org/Versions/v3/3.5/changesets/" name="viewed here">.
36 <sect1>Copyright disclaimer adjustments
37 <p>Squid sources are now administered by the Squid Software Foundation on
38 behalf of the Squid Project and community.
40 <p>This version of Squid contains initial changes to streamline copyright
41 declarations in Squid sources and related metafiles. No functionality
42 or licensing changes are intended.
44 <p>Once completed, the changes will consistently declare Squid contributors
45 (listed in CONTRIBUTORS and represented by the Squid Software Foundation) as
46 Squid copyright owners while referring the reader to the COPYING file for GPL
47 licensing details. The boilerplate with the above information is provided.
49 <p>These changes do not affect copyright rights of individuals or organizations.
50 We are simply confirming the fact that there are many Squid copyright owners,
51 just like there are many Linux kernel copyright owners. We are also providing
52 a simple, consistent way to document that fact.
55 <sect>Major new features since Squid-3.4
56 <p>Squid 3.5 represents a new feature release above 3.4.
58 <p>The most important of these new features are:
60 <item>Support libecap v1.0
61 <item>Authentication helper query extensions
62 <item>Support named services
63 <item>Upgraded squidclient tool
64 <item>Helper support for concurrency channels
65 <item>Native FTP Relay
66 <item>Receive PROXY protocol, Versions 1 & 2
67 <item>Basic authentication MSNT helper changes
70 Most user-facing changes are reflected in squid.conf (see below).
73 <sect1>Support libecap v1.0
74 <p>Details at <url url="http://wiki.squid-cache.org/Features/eCAP">.
76 <p>The new libecap version allows Squid to better check the version of
77 the eCAP adapter being loaded as well as the version of the eCAP library
80 <p>Squid-3.5 can support eCAP adapters built with libecap v1.0,
81 but no longer supports adapters built with earlier libecap versions
85 <sect1>Authentication helper query extensions
86 <p>Details at <url url="http://www.squid-cache.org/Doc/config/auth_param/">.
88 <p>The new <em>key_extras</em> parameter allows sending of additional
89 details to the authentication helper beyond the minimum required for
90 the HTTP authentication. This is primarily intended to allow switching
91 of authentication databases based on criteria such as client IP subnet,
92 Squid receiving port, or in reverse-proxy the requested domain name.
94 <p>In theory any <em>logformat</em> code may be used, however only the
95 codes which have available details at the time of authentication
96 will send any meaningful detail.
99 <sect1>Support named services
100 <p>Details at <url url="http://wiki.squid-cache.org/MultipleInstances">.
101 <p>Terminology details at <url url="http://wiki.squid-cache.org/Features/SmpScale#Terminology">.
103 <p>The command line option <em>-n</em> assigns a name to the Squid service
104 instance to be used as a unique identifier for all SMP processes run as
105 part of that instance. This allows multiple instances of Squid service to
106 be run on a single machine without background SMP systems such as shared
107 memory and inter-process communication becoming confused or requiring
108 additional configuration.
110 <p>A service name is always used. When the <em>-n</em> option is missing
111 from the command line the default service name is <em>squid</em>.
113 <p>When multiple instances are being run the <em>-n</em> service name is
114 required to target all other options such as <em>-z</em> or <em>-k</em>
115 commands at the correct service.
117 <p>The squid.conf macro ${service_name} is added to provide the service name
118 of the process parsing the config.
121 <sect1>Upgraded squidclient tool
122 <p>Details at <url url="http://www.squid-cache.org/Versions/v3/3.5/manuals/squidclient.html">.
124 <p>The <em>squidclient</em> has begun the process of upgrading to support
125 protocols other than HTTP.
128 <p>The tool displays the server response message on STDOUT unless the <em>-q</em>
129 command line option is used. Error messages will be output to STDERR.
130 All other possible output is considered debug and output to STDERR using
131 a range of debug verbosity levels (currently 1, 2 and 3).
133 <p>When the <em>-v</em> command line option is used debugging is enabled.
134 The level of debug display is raised for each repetition of the option.
137 <p>When <em>--ping</em> is given the tool will send its message repeatedly
138 using whichever protocol that message has been formatted for.
139 Optional parameters to limit the number of pings and their frequency are
142 <p>Older tool versions also provide this feature but require the loop count
143 parameter to be set to enable use of the feature.
146 <p>When Squid is built with the GnuTLS encryption library the tool is able
147 to open TLS (or SSL/3.0) connections to servers.
149 <p>The <em>--https</em> option enables TLS using default values.
151 <p>The <em>--cert</em> option specifies a file containing X.509 client
152 certificate and private key in PEM format to be loaded for use. Multiple
153 certificates are supported and the option may be used multiple times to
155 The default is not to use a client certificate.
157 <p>The <em>--params</em> option specifies a library specific set of parameters
158 to be sent to the library for configuring the security context.
159 See <url url="http://gnutls.org/manual/html_node/Priority-Strings.html"> for
160 available GnuTLS parameters.
162 <p>The <em>--trusted-ca</em> option specifies a file in PEM format containing
163 one or more Certificate Authority (CA) certificates used to verify the
164 remote server. This option may be used multiple times to load additional
165 CA certificate lists.
166 The default is not to use any CA, nor trust any server.
168 <p>Anonymous TLS (using non-authenticated Diffi-Hellman or Elliptic Curve
169 encryption) is available with the <em>--anonymous-tls</em> option.
170 The default is to use X.509 certificate encryption instead.
172 <p>When performing TLS/SSL server certificates are always verified, the
173 results shown at debug level 3. The encrypted type is displayed at debug
174 level 2 and the connection is used to send and receive the messages
175 regardless of verification results.
178 <sect1>Helper support for concurrency channels
179 <p>Helper concurrency greatly reduces the communication lag between Squid
180 and its helpers allowing faster transaction speeds even on sequential
183 <p>The Digest authentication, Store-ID, and URL-rewrite helpers packaged
184 with Squid have been updated to support concurrency channels. They will
185 auto-detect the <em>channel-ID</em> field and will produce the appropriate
187 With these helpers concurrency may now be set to 0 or any higher number as desired.
190 <sect1>Native FTP Relay
191 <p>Details at <url url="http://wiki.squid-cache.org/Features/FtpRelay">.
193 <p>Squid is now capable of accepting native FTP commands and relaying native
194 FTP messages between FTP clients and FTP servers. Native FTP commands
195 accepted at ftp_port are internally converted or wrapped into HTTP-like
196 messages. The same happens to Native FTP responses received from FTP origin
197 servers. Those HTTP-like messages are shoveled through regular access
198 control and adaptation layers between the FTP client and the FTP origin
199 server. This allows Squid to examine, adapt, block, and log FTP exchanges.
200 Squid reuses most HTTP mechanisms when shoveling wrapped FTP messages. For
201 example, http_access and adaptation_access directives are used.
203 <p>FTP Relay is a new, experimental, complex feature that has seen limited
204 production exposure. Some Squid modules (e.g., caching) do not currently
205 work with native FTP proxying, and many features have not even been tested
206 for compatibility. Test well before deploying!
208 <p>Native FTP proxying differs substantially from proxying HTTP requests with
209 <em>ftp://</em> URIs because Squid works as an FTP server and receives
210 actual FTP commands (rather than HTTP requests with FTP URLs).
212 <p>FTP Relay highlights:
214 <item>Added ftp_port directive telling Squid to relay native FTP commands.
215 <item>Active and passive FTP support on the user-facing side; require
216 passive connections to come from the control connection source IP
218 <item>IPv6 support (EPSV and, on the user-facing side, EPRT).
219 <item>Intelligent adaptation of relayed FTP FEAT responses.
220 <item>Relaying of multi-line FTP control responses using various formats.
221 <item>Support relaying of FTP MLSD and MLST commands (RFC 3659).
222 <item>Several Microsoft FTP server compatibility features.
223 <item>ICAP/eCAP support (at individual FTP command/response level).
224 <item>Optional "current FTP directory" tracking with the assistance of
225 injected (by Squid) PWD commands (cannot be 100% reliable due to
226 symbolic links and such, but is helpful in some common use cases).
227 <item>No caching support -- no reliable Request URIs for that (see above).
230 <sect1>Receive PROXY protocol, Versions 1 & 2
231 <p>More info at <url url="http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt">
233 <p>PROXY protocol provides a simple way for proxies and tunnels of any kind to
234 relay the original client source details without having to alter or understand
235 the protocol being relayed on the connection.
237 <p>Squid currently supports receiving HTTP traffic from a client proxy using this protocol.
238 An http_port which has been configured to receive this protocol may only be used to
239 receive traffic from client software sending in this protocol.
240 HTTP traffic without the PROXY header is not accepted on such a port.
242 <p>The <em>accel</em> and <em>intercept</em> options are still used to identify the HTTP
243 traffic syntax being delivered by the client proxy.
245 <p>Squid can be configured by adding an <em>http_port</em>
246 with the <em>require-proxy-header</em> mode flag. The <em>proxy_protocol_access</em>
247 must also be configured with <em>src</em> ACLs to whitelist proxies which are
248 trusted to send correct client details.
250 <p>Forward-proxy traffic from a client proxy:
252 acl frontend src 192.0.2.1
253 http_port 3128 require-proxy-header
254 proxy_protocol_access allow frontend
257 <p>Intercepted traffic from a client proxy or tunnel:
259 acl frontend src 192.0.2.2
260 http_port 3128 intercept require-proxy-header
261 proxy_protocol_access allow frontend
264 <p>Reverse-proxy traffic from a frontend load balancer sending PROXY protocol:
266 acl frontend src 192.0.2.3
267 http_port 3128 accel require-proxy-header
268 proxy_protocol_access allow frontend
271 <p><em>Known Issue:</em>
272 Use of <em>require-proxy-header</em> on <em>https_port</em> and <em>ftp_port</em> is not supported.
275 <sect1>Basic authentication MSNT helper changes
277 <p>The authentication helper previously known as <em>basic_msnt_auth</em> has
278 been deprecated and renamed to <em>basic_smb_lm_auth</em> to reflect that
279 it only performs SMB LanMan protocol(s) instead of modern MS authentication
282 <p>The <em>basic_smb_lm_auth</em> helper has been remodelled and no longer uses
283 configuration files. The Doman Controller servers are now configured via
284 command line parameters and user credentials are looked up in each DC in the
285 order configured until one matches or all have confirmed a non-match.
287 <p>The <em>MSNT-multi-domain</em> helper provides the same functionality and
288 is also deprecated. It will be removed in the Squid-3.6 series.
292 <sect>Changes to squid.conf since Squid-3.4
294 There have been changes to Squid's configuration file since Squid-3.4.
296 <p>Squid supports reading configuration option parameters from external
297 files using the syntax <em>parameters("/path/filename")</em>. For example:
299 acl whitelist dstdomain parameters("/etc/squid/whitelist.txt")
302 <p>The squid.conf macro <em>${service_name}</em> is added to provide the service name
303 of the process parsing the config.
305 <p>There have also been changes to individual directives in the config file.
307 This section gives a thorough account of those changes in three categories:
310 <item><ref id="newtags" name="New tags">
311 <item><ref id="modifiedtags" name="Changes to existing tags">
312 <item><ref id="removedtags" name="Removed tags">
316 <sect1>New tags<label id="newtags">
319 <tag>collapsed_forwarding</tag>
320 <p>Ported from Squid-2 with no configuration or visible behaviour changes.
321 Collapsing of requests is performed across SMP workers.
323 <tag>ftp_client_idle_timeout</tag>
324 <p>New directive controlling how long to wait for an FTP request on a
325 client connection to Squid <em>ftp_port</em>.
326 <p>Many FTP clients do not deal with idle connection closures well,
327 necessitating a longer default timeout (30 minutes) than
328 <em>client_idle_pconn_timeout</em> used for incoming HTTP requests (2
330 <p>The current default may be changed as we get more experience with FTP relaying.
333 <p>New configuration directive to accept and relay native FTP
334 commands. Typically used for port 21 traffic. By default, native
335 FTP commands are not accepted.
337 <tag>proxy_protocol_access</tag>
338 <p>New directive to control which clients are permitted to open PROXY
339 protocol connections on a port flagged with <em>require-proxy-header</em>.
342 <p>New configuration directive to enable/disable sending cached content
343 based on ACL selection. ACL can be based on client request or cached
346 <tag>sslproxy_cert_sign_hash</tag>
347 <p>New directive to set the hashing algorithm to use when signing generated certificates.
349 <tag>sslproxy_session_cache_size</tag>
350 <p>New directive which sets the cache size to use for TLS/SSL sessions cache.
352 <tag>sslproxy_session_ttl</tag>
353 <p>New directive to specify the time in seconds the TLS/SSL session is valid.
355 <tag>store_id_extras</tag>
356 <p>New directive to send additional lookup parameters to the configured
357 Store-ID helper program. It takes a string which may contain logformat %macros.
358 <p>The Store-ID helper input format is now:
360 [channel-ID] url [extras]
362 <p>The default value for extras is: "%>a/%>A %un %>rm myip=%la myport=%lp"
364 <tag>store_miss</tag>
365 <p>New configuration directive to enable/disable caching of MISS responses.
366 ACL can be based on any request or response details.
368 <tag>url_rewrite_extras</tag>
369 <p>New directive to send additional lookup parameters to the configured
370 URL-rewriter/redirector helper program. It takes a string which may
371 contain logformat %macros.
372 <p>The url rewrite and redirector helper input format is now:
374 [channel-ID] url [extras]
376 <p>The default value for extras is: "%>a/%>A %un %>rm myip=%la myport=%lp"
380 <sect1>Changes to existing tags<label id="modifiedtags">
384 <p>Deprecated type <em>tag</em>. Use type <em>note</em> with 'tag' key
386 <p>New type <em>adaptation_service</em> to match the name of any
387 icap_service, ecap_service, adaptation_service_set, or
388 adaptation_service_chain that Squid has used (or attempted to use)
389 for the HTTP transaction so far.
390 <p>New type <em>at_step</em> to match the current SSL-Bump processing step.
391 Never matches and should not be used outside of <em>ssl_bump</em>.
392 <p>New types <em>ssl::server_name</em> and <em>ssl::server_name_regex</em>
393 to match server name from various sources (CONNECT authority name,
394 TLS SNI domain, or X.509 certificate Subject Name).
396 <tag>auth_param</tag>
397 <p>New parameter <em>key_extras</em> to send additional parameters to
398 the authentication helper.
401 <p>New support for larger than 32KB objects in both <em>rock</em> type
402 cache and shared memory cache.
403 <p>New <em>slot-size=N</em> option for rock cache to specify the database
404 slot/page size when small slot sizes are desired. The default and
405 maximum slot size is 32KB.
406 <p>Removal of old rock cache dir followed by <em>squid -z</em> is required
407 when upgrading from earlier versions of Squid.
408 <p><em>COSS</em> storage type is formally replaced by Rock storage type.
409 COSS storage type and all COSS specific options are removed.
411 <tag>cache_peer</tag>
412 <p>New <em>standby=N</em> option to retain a set of N open and unused
413 connections to the peer at virtually all times to reduce TCP handshake
415 <p>These connections differ from HTTP persistent connections in that they
416 have not been used for HTTP messaging (and may never be). They may be
417 turned into persistent connections after their first use subject to the
418 same keep-alive critera any HTTP connection is checked for.
419 <p>Squid-2 option <em>idle=</em> replaced by <em>standby=</em>.
420 <p>NOTE that standby connections are started earlier and available in
421 more circumstances than squid-2 idle connections were. They are
422 also spread over all IPs of the peer.
424 <tag>configuration_includes_quoted_values</tag>
425 <p>Regex pattern values cannot be parsed in parts of squid.conf when this
426 directive is configured to <em>ON</em>. Instead of quoted strings Squid
427 now accepts regex \-escaped characters (including escaped spaces) in all
430 <tag>external_acl_type</tag>
431 <p>New format code <em>%ssl::>sni</em> to send SSL client SNI.
432 <p>New format code <em>%ssl::<cert_subject</em> to send SSL server certificate DN.
433 <p>New format code <em>%ssl::<cert_issuer</em> to send SSL server certificate issuer DN.
434 <p>New response kv-pair <em>clt_conn_tag=</em> to associates a given tag with the client TCP connection.
436 <tag>forward_max_tries</tag>
437 <p>Default value increased to <em>25 destinations</em> to allow better
438 contact and IPv4 failover with domains using long lists of IPv6
442 <p>Converted into an Access List with allow/deny value driven by ACLs
443 using Squid standard first line wins matching basis.
444 <p>The old values of <em>on</em> and <em>off</em> imply <em>allow all</em>
445 and <em>deny all</em> respectively and are now deprecated.
446 Do not combine use of on/off values with ACL configuration.
449 <p><em>protocol=</em> option altered to accept protocol version details.
450 Currently supported values are: HTTP, HTTP/1.1, HTTPS, HTTPS/1.1
451 <p>New option <em>require-proxy-header</em> to mark ports receiving PROXY
452 protocol version 1 or 2 traffic.
454 <tag>https_port</tag>
455 <p><em>protocol=</em> option altered to accept protocol version details.
456 Currently supported values are: HTTP, HTTP/1.1, HTTPS, HTTPS/1.1
459 <p>New format code <em>%credentials</em> to log the client credentials token.
460 <p>New format code <em>%ssl::>sni</em> to TLS client SNI sent to Squid.
461 <p>New format code <em>%tS</em> to log transaction start time in
462 "seconds.milliseconds" format, similar to the existing access.log
463 "current time" field (%ts.%03tu) which logs the corresponding
464 transaction finish time.
465 <p>New format codes <em>%<rs</em> and <em>%>rs</em> to log request URL
466 scheme from client or sent to server/peer respectively.
467 <p>New format codes <em>%<rd</em> and <em>%>rd</em> to log request URL
468 domain from client or sent to server/peer respectively.
469 <p>New format codes <em>%<rP</em> and <em>%>rP</em> to log request URL
470 port from client or sent to server/peer respectively.
473 <p>Bumping 'modes' redesigned as 'actions' and ACLs evaluated repeatedly in a number of steps.
474 <p>Renamed <em>server-first</em> as <em>bump</em> action.
475 <p>Renamed <em>none</em> as <em>splice</em> action.
476 <p>New actions <em>peek</em> and <em>stare</em> to receive client or server
477 certificate while preserving the ability to later decide between bumping
478 or splicing the connections later.
479 <p>New action <em>terminate</em> to close the client and server connections.
481 <tag>url_rewrite_program</tag>
482 <p>New response kv-pair <em>clt_conn_tag=</em> to associates a given tag with the client TCP connection.
486 <sect1>Removed tags<label id="removedtags">
489 <tag>cache_dns_program</tag>
490 <p>DNS external helper interface has been removed. It was no longer
491 able to provide high performance service and the internal DNS
492 client library with multicast DNS cover all modern use-cases.
494 <tag>dns_children</tag>
495 <p>DNS external helper interface has been removed.
497 <tag>hierarchy_stoplist</tag>
498 <p>Removed. The old directive values prohibiting CGI and dynamic content
499 going to cache_peer are no longer relevant.
500 <p>The functionality provided by this directive can be configured
501 using <em>always_direct allow</em> if still needed.
506 <sect>Changes to ./configure options since Squid-3.4
508 There have been some changes to Squid's build configuration since Squid-3.4.
510 This section gives an account of those changes in three categories:
513 <item><ref id="newoptions" name="New options">
514 <item><ref id="modifiedoptions" name="Changes to existing options">
515 <item><ref id="removedoptions" name="Removed options">
519 <sect1>New options<label id="newoptions">
523 <p>Used when cross-compiling Squid.
524 <p>The path and name of a compiler for building cf_gen and related
525 tools used in the compile process.
527 <tag>BUILDCXXFLAGS=</tag>
528 <p>Used when cross-compiling Squid.
529 <p>C++ compiler flags used for building cf_gen and related
530 tools used in the compile process.
532 <tag>--without-gnutls</tag>
533 <p>New option to explicitly disable use of GnuTLS encryption library.
534 Use of this library is auto-enabled if v3.1.5 or later is available.
535 <p>It is currently only used by the squidclient tool.
537 <tag>--without-mit-krb5</tag>
538 <p>New option to explicitly disable use of MIT Kerberos library.
539 Default is to auto-detect and use if possible.
540 <p>Only one Kerberos library may be built against.
542 <tag>--without-heimdal-krb5</tag>
543 <p>New option to explicitly disable use of Hiemdal Kerberos library.
544 Default is to auto-detect and use if possible.
545 <p>Only one Kerberos library may be built against.
547 <tag>--without-gnugss</tag>
548 <p>New option to explicitly disable use of GNU GSSAPI library for Kerberos.
549 Default is to auto-detect and use if possible.
550 <p>Only one Kerberos library may be built against.
554 <sect1>Changes to existing options<label id="modifiedoptions">
557 <tag>--enable-icap-client</tag>
558 <p>Deprecated. ICAP client is now auto-enabled.
559 Use --disable-icap-client to disable if you need to.
564 <sect1>Removed options<label id="removedoptions">
567 <tag>--disable-internal-dns</tag>
568 <p>DNS external helper interface has been removed. It was no longer
569 able to provide high performance service and the internal DNS
570 client library with multicast DNS cover all modern use-cases.
572 <tag>--enable-ssl</tag>
573 <p>Removed. Use <em>--with-openssl</em> to enable OpenSSL library support.
575 <tag>--with-coss-membuf-size</tag>
576 <p>The COSS cache type has been removed.
577 It has been replaced by <em>rock</em> cache type.
579 <tag>--with-krb5-config</tag>
580 <p>Removed. The Kerberos library is auto-detected now.
581 <p>Use <em>--with/--without-mit-krb5</em>, <em>--with/--without-heimdal-krb5</em>, or
582 <em>--with/--without-gnugss</em> options for specific library selection if necesary.
587 <sect>Regressions since Squid-2.7
589 <p>Some squid.conf options which were available in Squid-2.7 are not yet available in Squid-3.5
591 <p>If you need something to do then porting one of these from Squid-2 to Squid-3 is most welcome.
593 <sect1>Missing squid.conf options available in Squid-2.7
596 <tag>broken_vary_encoding</tag>
597 <p>Not yet ported from 2.6
599 <tag>cache_peer</tag>
600 <p><em>monitorinterval=</em> not yet ported from 2.6
601 <p><em>monitorsize=</em> not yet ported from 2.6
602 <p><em>monitortimeout=</em> not yet ported from 2.6
603 <p><em>monitorurl=</em> not yet ported from 2.6
605 <tag>cache_vary</tag>
606 <p>Not yet ported from 2.6
609 <p>Not yet ported from 2.6
611 <tag>external_refresh_check</tag>
612 <p>Not yet ported from 2.7
614 <tag>location_rewrite_access</tag>
615 <p>Not yet ported from 2.6
617 <tag>location_rewrite_children</tag>
618 <p>Not yet ported from 2.6
620 <tag>location_rewrite_concurrency</tag>
621 <p>Not yet ported from 2.6
623 <tag>location_rewrite_program</tag>
624 <p>Not yet ported from 2.6
626 <tag>refresh_pattern</tag>
627 <p><em>stale-while-revalidate=</em> not yet ported from 2.7
628 <p><em>ignore-stale-while-revalidate=</em> not yet ported from 2.7
629 <p><em>negative-ttl=</em> not yet ported from 2.7
631 <tag>refresh_stale_hit</tag>
632 <p>Not yet ported from 2.7
634 <tag>update_headers</tag>
635 <p>Not yet ported from 2.7
641 Copyright (C) 1996-2015 The Squid Software Foundation and contributors
643 Squid software is distributed under GPLv2+ license and includes
644 contributions from numerous individuals and organizations.
645 Please see the COPYING and CONTRIBUTORS files for details.