1. The web server we were working with originally was misconfigured. Since it was apache, it had a setting
"^Moz.*" downgrade-1.0 force-response-1.0
This setting forced ALL browsers to use HTTP/1.0. So, all you apache admins, please DON'T put a setting on your web server to downgrade HTTP!
2. The second cause I found belonged to Blue Coat proxy. By default (if you have authentication enabled) any SSL connection going through a Blue Coat proxy will "Act" like HTTP/1.0. This is due to the authentication "mode" being set to 'auto' by default.
When the proxy has to 'auto' determine the mode, and each request will have to go through the process and the proxy treats them all as a new connection, forcing the SSL to re-negotiate and close each one. Changing it to "Proxy IP" is recommended by Blue Coat.
If you have authentication on your Blue Coat, then I would HIGHLY recommend changing the mode to the Proxy IP option. ALL your SSL traffic will be reduced, lowering your cpu utilization, network load, and all SSL web server loads as well!
Did this solve your problem?
Sorry this didn't help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.