Why is it that Secured HTTP Connection (https) is Slower then than typical HTTP (http)?
Just interested in knowing only.
Thanks.
Why is it that Secured HTTP Connection (https) is Slower then than typical HTTP (http)?
Just interested in knowing only.
Thanks.
To open a TCP/IP connection requires 3 packets to be exchanged between the client and the server. The connection is then considered established, and the client can submit its request.
When SSL is added on top of the TCP/IP connection there are several additional interactions that have to happen before the connection is considered established.
Unless the latency is negligible between the client and the server (read, the same network), then it is likely that this additional latency, due to the additional round trips to exchange SSL handshaking data, not the CPU overhead of calculating the key material, is the major factor in the delay in establishing an SSL connection.
More information about TCP/IP connection establishment
More information about SSL/TLS handshaking
In simple words: Because it encrypts and decrypts the traffic, this requires processing on both sides (the server and the client).
As mentioned by other people there is the encryption and decryption steps for all transfers. There are two other issues though:
Jeff Moser just posted a good article on this explaining the ins and outs, handshaking etc.
http://www.moserware.com/2009/06/first-few-milliseconds-of-https.html
To add to pauska's answer:
Most web server platforms can add hardware/software to improve the performance of SSL on the server. This product does this.
Because it takes a little bit of time to encrypt the content, and the encryption generally increases the size of the content.
i have that establish secure connetion lag too... i look in chrome advanced parameter. scroll down to https/ssl and deleted all certificate relative to comodo (found them in the second or third tab, din't remember), never got that establish secure connection lag again hope that help