Can you please file a bug report on the issue?
There is maybe a way to solve it if will be needed in the future and
also it has a significant effect on errors.
http://bugs.squid-cache.org/
If it's too hard let me now via email and I will fill the blanks about
the server version and settings for a test case of the issue.
Eliezer
On 04/22/2014 11:25 AM, tomsl wrote:
I managed to solve the problem. It seems that this problem only occurs when
using TLS 1.0 which was the highest allowed by the backend servers by
default. Enabling TLS 1.2 on the servers and telling squid to use this fixed
the issue.
Hopefully this will help someone else experiencing the same issue!
