Thank you. It doesn't seem that the "originserver" makes a difference to
may case though.
I was able to resolve my issue after I understood that I forgot to pay
attention to cookies. The API expects the client to use cookies, which I
didn't do until now, which resulted in a continuous "401
I think, you should dig in this direction:
# acl aclname ssl_error errorname
# # match against SSL certificate validation error [fast]
# #
# # For valid error names see in
/usr/local/squid/share/errors/templates/error-details.txt
# # template file.
# #
# # The
Le 16/03/2018 à 13:43, Yuri a écrit :
> I guess better way to do this is create special ACL to catch exactly
> certificate error and then redirect by 302 using deny_info to proxy
> page with explanation and certificate.
This sounds like the way to go.
I just removed the root certificate from
I guess better way to do this is create special ACL to catch exactly
certificate error and then redirect by 302 using deny_info to proxy page
with explanation and certificate.
Sadly, however I have no full solution for this logic (we're simple
install proxy certificate manually), but idea exists
Hi,
I have Squid + SquidGuard + SquidAnalyzer running on my LAN server as a
transparent cache + filtering proxy, and it's working real nicely.
When a client in my company wants to connect to the wifi, all he or she
has to do is this:
1. Connect to http://nestor.microlinux.lan
2. Download the
