From 565b91d89f0412c5ccd43940d2a3f388d60c348e Mon Sep 17 00:00:00 2001 From: Amos Jeffries Date: Tue, 15 Nov 2016 19:49:07 +1300 Subject: [PATCH] Docs: release notes for ICAP Trailers --- doc/release-notes/release-5.sgml | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/doc/release-notes/release-5.sgml b/doc/release-notes/release-5.sgml index 16b42b010b..ac4dafd670 100644 --- a/doc/release-notes/release-5.sgml +++ b/doc/release-notes/release-5.sgml @@ -36,26 +36,27 @@ The Squid-4 change history can be - and +ICAP Trailers +

Details in -

SSLv2 is not fit for purpose. Squid no longer supports being configured with - any settings regarding this protocol. That includes settings manually disabling - its use since it is now forced to disable by default. Also settings enabling - various client/server workarounds specific to SSLv2 are removed. +

The Trailers feature from HTTP is being proposed for addition to ICAP, + with some modifications. -

SSLv3 is not fit for purpose. Squid still accepts configuration, but use - is deprecated and will be removed entirely in a future version. - Squid default behavour is to follow the TLS built in negotiation mechanism - which prefers the latest TLS version. But also to accept downgrades to SSLv3. - Use tls-options=NO_SSLv3 to disable SSLv3 support completely. +

This implementation complies with version -01 of that draft: + + Announces ICAP Trailer support via the ICAP Allow request header field. + Parses the ICAP response trailer if and only if the ICAP server signals + its presence by sending both Trailer header and Allow/trailers in the + ICAP response. + + +

For now Squid logs and ignores all parsed ICAP header fields. Changes to squid.conf since Squid-4 -- 2.47.3