On 2016-06-14, Ted Wynnychenko <ted....@comcast.net> wrote: > This really isn't a big deal; but as more sites have started using https, and > as > tools such as relayd and squid (and others?) have developed ways to "inject" > https certificates on the fly, I am wondering if there is a way to create > https > certificates based solely on the requested URL in a connection attempt using > an > internal CA to avoid the certificate errors with blocked HTTPS connections?
How are you identifying connections to block?
