I'm looking for the ACL / option / feature that will prevent SQUID from
presenting an error page for reasons like "ERR_INVALID_REQ" and any other
reasons.
Basically, id's want something like this:
acl 400 http_status 400
deny_info TCP_RESET 400
But, it appears that the ACLs are not parsed when
: Kristopher Lalletti
Cc: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] cache_peer directive with SNI
Have you looked at the options forceddomain and ssldomain under the cache_peer
directive? Those may be just what you need.
On Tue, Jun 21, 2016 at 8:14 PM, Kristopher Lalletti
Hi All,
I'm replacing an Apache setup as a reverse-proxy with Squid v3.5, and I've hit
a small snag.
Basically, I need to tell squid to pass the proper SSL SNI name to the backend
webserver which is accessed via SSL, and naturally, the SSL SNI service-name
(service.foo.com) is not the server
