When SslBump is activated, Squid responds to CONNECT request
with HTTP 200 "Connection established" and switches to SSL
encryption on the connection.
Added ssl_bump ACL. The ACL controls which CONNECT requests to
an http_port marked with an sslBump flag are actually "bumped".
This was needed to bypass the bump and tunnel requests to sites
that Squid cannot handle well (with or without the bump), with
other use cases likely to surface.
By default, no requests are bumped. Squid warns if http_port(s)
have SslBump but no ssl_bump ACL was configured.
The ACL applies to all http_ports, but I suspect that, if
needed, specific ACL rules can distinguish ports using
"myport".
Added ERR_SECURE_CONNECT_FAIL that is returned when we cannot
secure the established connection with the server. Formerly,
ERR_CONNECT_FAIL was returned.
/*
- * $Id: client_side_request.h,v 1.35 2008/02/08 18:27:59 rousskov Exp $
+ * $Id: client_side_request.h,v 1.36 2008/02/11 22:33:48 rousskov Exp $
*
*
* SQUID Web Proxy Cache http://www.squid-cache.org/
StoreEntry *loggingEntry_;
ConnStateData::Pointer conn_;
+#if USE_SSL
+public:
+ bool sslBumpNeeded() const;
+ void sslBumpStart();
+ void sslBumpEstablish(comm_err_t errflag);
+#endif
+
#if ICAP_CLIENT
public: