We now have a long list of sites in this temporary solution, and it seems we have also have more and more sites with the issue. We are in 220.127.116.11, any news for a real solution or if we still should use the workaround?
What sites are you seeing this problem with? Is it the identical error from the original thread?
The original problem was caused by POODLE.
Problem is: it is an erratic issue, usually happening when users are using MCP to redirect web traffic to the McAfee SaaS. As far as I know we do not have the issue with on Premise proxies.