> It is most likely that your clients browsers or SSL libraries are > missing AES-256 support or are getting stuck negotiating to use a > version of TLS/SSL which supports it. > > Amos > Ok, but if I turn off proxy setting in clients and allow a direct connection to the internet, all works well. So I think there is something strange in my proxy machine/configuration that denies some packets to flow correctly through it. Client-side, if I leave proxy enabled and try to contact aes-256 sites, in netstat I can see the connection in SYN_SENT state, so that I think that somewhere some packets are dropped... -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-1-and-https-ssl-aes256-issue-tp4655250p4655257.html Sent from the Squid - Users mailing list archive at Nabble.com.
