6 ms·
Upon further investigation, it's not just the API, it's the entire site. A significant cause of the issue is their SSL implementation. Specifically it negotiat
by wamatt 14y ago
Upon further investigation, it's not just the API, it's the entire site.
A significant cause of the issue is their SSL implementation. Specifically it negotiates a new connection every time instead of resuming the session, eek!
http://security.stackexchange.com/questions/5511/ssl-session-resumption-and-ids http://security.stackexchange.com/questions/5511/ssl-session...
https://www.ssllabs.com/ssltest/analyze.html?d=github%2ecom&s=207%2e97%2e227%2e243 https://www.ssllabs.com/ssltest/analyze.html?d=github%2ecom&...
- nodesocket 14y agoIs this a problem with the default setup of Nginx out of the box, or has GitHub intentionally disabled session resumption?
- wamatt 14y agoHaven't tried the latest nginx install, but according to the wiki, ssl_session_cache controls this, and is set to 'none' by default. http://wiki.nginx.org/HttpSslModule http://wiki.nginx.org/HttpSslModule As for Github, could just be a misconfiguration, or perhaps they had some more deliberate reason in mind. Good news is I just received confirmation from one of the ops guys. He says they know about it, and are working on a fix. :)
- nodesocket 14y agoAwesome, GitHub ops on it. :) Curious if there will be a speed improvement once they enable session resumption. Any idea why the default in nginx is: none. Soft off: nginx says to a client that session can be resued, but nginx actually never reuses them. Seems like a bad default to not cache.