From 9deb9a42a969fd50086d14982916c702f12ad4bc Mon Sep 17 00:00:00 2001 From: Amos Jeffries Date: Sat, 12 Jul 2014 21:23:40 -0700 Subject: [PATCH] Docs: update mention that HTTPS no longer supported --- doc/release-notes/release-3.5.sgml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/release-notes/release-3.5.sgml b/doc/release-notes/release-3.5.sgml index 43638c9248..d4ac86d8be 100644 --- a/doc/release-notes/release-3.5.sgml +++ b/doc/release-notes/release-3.5.sgml @@ -171,12 +171,12 @@ Most user-facing changes are reflected in squid.conf (see below). relay the original client source details without having to alter or understand the protocol being relayed on the connection. -

Squid currently supports receiving version 1 or 2 of the protocol. +

Squid currently supports receiving HTTP via version 1 or 2 of the protocol. A port which has been configured to receive this protocol may only be used to receive traffic from client software sending in this protocol. Regular forward-proxy HTTP traffic is not accepted. -

Squid can be configured by adding an http_port or https_port +

Squid can be configured by adding an http_port with the proxy-surrogate mode flag. The proxy_forwarded_access must also be configured with src ACLs to whitelist proxies which are trusted to send correct client details. @@ -187,6 +187,10 @@ Most user-facing changes are reflected in squid.conf (see below). proxy_forwarded_access allow localhost +

Know Issue: Due to design issues HTTPS traffic is not yet accepted + over this protocol. So use of proxy-surrogate on https_port + is not supported. + Changes to squid.conf since Squid-3.4

-- 2.47.3