On 01/01/15 00:11, James Harper wrote: > The helper connects to the IP:port and tries to obtain the certificate, and > then caches the result (in an sqlite database). If it can't do so within a > fairly short time it returns failure (but keeps trying a bit longer and > caches it for next time). Alternatively if the IP used to be SSL but is now > timing out it returns the previously cached value. Negative results are > cached for an increasing amount of time each time it fails, on the basis that > it probably isn't SSL. That sounds great James! I'd certainly like to take a look at it too
However, you say "SSL" - did you mean "HTTPS"? ie discovering a ip:port is a IMAPS server doesn't really help squid talk to it - surely you want to discover HTTPS servers - and everything else should be pass-through/splice? -- Cheers Jason Haar Corporate Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
