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 one of the clients and then tried to open a few HTTPS sites. Invariably, I get the follwoing error code : SEC_ERROR_UNKNOWN_ISSUER So how would I tell Squid in its own syntax to go to http://nestor.microlinux.lan when it encounters such an error ? Is this a trivial task, or more complicated to put in practice ? BTW, this would be the last piece in my puzzle, and my installation would be perfect if I got this to work. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@xxxxxxxxxxxxx Tél. : 04 66 63 10 32 _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
