I have my logformat as follows.
logformat jsonformat {"Client Hostname":"%>A","Source IP":"%>a","HTTP Method
":"%rm","HTTP Protocol version":"%rv","Request Domain":"%>rd","Port":"%>rP",
"User Agent":"%{User-Agent}>h","Request Size":"%>st","Reply
Size":"%Hs","Request Status":"%Ss","Server FQDN":"
%
On 11/21/19 9:25 AM, Monah Baki wrote:
> The certs/keys are legit from my company.
Is your signing certificate (i.e. wildcardcert.pem) a CA certificate? If
not, then you cannot use it to sign other certificates. SslBump with
dynamic certificate generation requires a CA certificate to sign the
gen
On 11/21/19 11:29 AM, Giles Coochey wrote:
> I believe Palo Alto and Bluecoats have a feature mechanism to provide
> the client with an appropriately broken cert , e.g. if the cert is
> expired, but has a trusted chain then it uses an expired cert with a
> trusted chain to the client, and if a cer
On 21/11/2019 12:51, Kassir Bariq wrote:
Hi,
You can add this line in your squid.conf
sslproxy_cert_error allow allowed_https_sites
this should fix your issue to bypass sites without a valid certificate.
I probably wouldn't do this blindly, either use a different acl such as
known_broken_
Hi,
You can add this line in your squid.conf
sslproxy_cert_error allow allowed_https_sites
this should fix your issue to bypass sites without a valid certificate.
Regards
Bariq
From: squid-users On Behalf Of
Berger J Nicklas
Sent: den 21 november 2019 10:16
To: squid-users
On 21/11/2019 09:16, Berger J Nicklas wrote:
We are using squid for both http and https whitelisting for egress.
Most of the whitelisting works fine but some specific once do not work.
We have tried this on this versions of squid 3.5(amazon linux 2),
4.1(centos7) and 4.4(centos8).
For instance
We are using squid for both http and https whitelisting for egress. Most of the
whitelisting works fine but some specific once do not work.
We have tried this on this versions of squid 3.5(amazon linux 2), 4.1(centos7)
and 4.4(centos8).
For instance when running yum update for redhat linux in aws
A colleague provided this squid.conf and now https working fine with curl as
well!
visible_hostname localhost
# Handling HTTP requests
http_port 3128
http_port 3129 intercept
acl allowed_http_sites dstdomain .microsoft.com
acl allowed_http_sites dstdomain .google.com
acl allowed_http_sites dstd
