HTTPS Common Sense Description

1 does the certificate have to be?

The certificate is required and HTTPS needs to be encrypted with the password in the certificate.

The server must be installed and the client does not need to be installed.

The client automatically downloads the certificate on the server, so there is no special impact on the client.

Process:

When the client is accessed over HTTPS, the server sends the certificate (only the public key) to the client, who determines whether the certificate is trustworthy in the CA that it has installed. If it is not trusted, there will be a warning prompt, and of course you can ignore the hint to continue the visit.

SSL Certificate features: Data encryption and identity authentication.

2 https too slow?

The first time the connection is established is about 10% slower, and once a valid HTTPS connection is established, there is little difference between the two protocols.

3 HTTPS may be faster than HTTP?

This can happen in the internal LANs of some large companies, as the company's gateways typically intercept and analyze all network traffic. However, when it encounters an HTTPS connection, it can only be released directly, because HTTPS cannot be interpreted. It is because of the lack of this interpretation process, so HTTPS becomes relatively fast.

Also attached:

Seven Misconceptions about https: http://www.ruanyifeng.com/blog/2011/02/seven_myths_about_https.html

This article is from the "Members Doukua" blog, make sure to keep this source http://dangzhiqiang.blog.51cto.com/7961271/1674190

HTTPS Common Sense Description