Re: [squid-users] Squid 3.1.20 is available

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Tue, 12 Jun 2012 10:57:29 +1200

On 12.06.2012 05:41, Christian wrote:
> Hi Amos,
>
> thank you, but
> signature file is missing :(
> There is no download link for signature file here:
> http://www.squid-cache.org/Versions/v3/3.1/
>
> Cheers
> Chris
>

Bit of annoying delay on the mirror pull. :-(
I've kicked it manually and seems to have worked. It should show up
within a few hours. Thanks.

Amos

> Am 11.06.2012 13:24, schrieb Amos Jeffries:
>> The Squid HTTP Proxy team is very pleased to announce the
>> availability of the Squid-3.1.20 release!
>>
>>
>> This release brings many bug fixes for issues found in earlier
>> releases.
>> Including a few outstanding minor security issues.
>>
>>
>> Of particular note are:
>>
>> * Bug 3466: Adaptation stuck on last single-byte body piece.
>>
>> This has been a uncommon but regular problem affecting Squid with
>> ICAP services. The hang behaviour only affects one client connection
>> for a limited time, but can be remotely triggered by certain server
>> responses.
>>
>>
>> * clientside_tos is now marking traffic properly again.
>>
>> This fixes a regression since 3.1.12.2
>>
>>
>> * URL parsing now accepts the full range of URI part delimiters from
>> RFC 3986.
>>
>> This affects URL-rewriters redirectors, and of course all traffic
>> incoming to Squid. Prior to this change Squid was accepting some
>> invalid syntaxes and rejecting a number of unusual but valid modern
>> URL syntax. With the change Squid better supports clients which need
>> these URL formats.
>>
>>
>> * Bug 3539: CONNECT server connection not closed correctly on
>> errors.
>>
>> Prior to this change server connections used for HTTPS or other
>> tunneled protocols could be left open and limit the available FD
>> resources.
>>
>>
>> * Bug 3390: Proxy auth data visible to scripts
>>
>> This is a minor security issue. Scripts are able to recover browser
>> headers sent to the proxy, which may include authentication
>> credentials.
>>
>>
>> * Support CoAP over HTTP (coap:// and coaps:// URLs)
>>
>> This is only support for relaying coap:// and coaps:// URL in HTTP
>> requests. There is one minor build issue in the 3.1.20 package with
>> libecap not supporting these URL schemes yet. A workaround patch is
>> being tested and should be available shortly in the daily updates.
>>
>>
>>
>> See the ChangeLog for more details and the list of other changes in
>> this release.
>>
>> All users of Squid-3 are advised to upgrade as soon as possible.
>>
>>
>> Please refer to the release notes at
>> http://www.squid-cache.org/Versions/v3/3.1/RELEASENOTES.html
>> when you are ready to make the switch to Squid-3.1
>>
>> This new release can be downloaded from our HTTP or FTP servers
>>
>> http://www.squid-cache.org/Versions/v3/3.1/
>> ftp://ftp.squid-cache.org/pub/squid/
>> ftp://ftp.squid-cache.org/pub/archive/3.1/
>>
>> or the mirrors. For a list of mirror sites see
>>
>> http://www.squid-cache.org/Download/http-mirrors.html
>> http://www.squid-cache.org/Download/mirrors.html
>>
>> If you encounter any issues with this release please file a bug
>> report.
>> http://bugs.squid-cache.org/
>>
>>
>> Amos Jeffries
Received on Mon Jun 11 2012 - 22:57:32 MDT

This archive was generated by hypermail 2.2.0 : Tue Jun 12 2012 - 12:00:03 MDT