> > 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? > Yes. That would be required for completeness, although maybe the certificate info would still be useful even if the underlying protocol wasn't http... James _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
