|
Myth Seven: HTTPS cannot be cached
Many people think that, for security reasons, the browser does not save the HTTPS cache locally. In fact, HTTPS can be cached as long as a specific command is used in the HTTP header.
Eric Lawrence, Microsoft's IE Project manager, wrote:
"It might be shocking, as long as HTTP headers allow this, and all versions of IE cache HTTPS content. For example, if the header command is cache-control:max-age=600, then this page will be cached by IE for 10 minutes. The cache policy of IE is independent of whether to use HTTPS protocol. (The behavior of other browsers in this respect is inconsistent, depending on the version you are using, so this is not discussed here.) )"
Firefox only caches https in memory by default. However, as long as there is cache-control:public in the header command, the cache is written to the hard disk. The image below shows that there is https content in Firefox's hard disk cache, and the header command is cache-control:public.
Myth Six: SSL certificates are expensive
If you search the Internet, you will find a lot of cheap SSL certificates, about 10 dollars a year, and a. com domain name of the annual fee is similar. And in fact, you can find a free SSL certificate.
In effect, a cheap certificate is certainly less than a certificate issued by a large institution, but almost all mainstream browsers accept the certificate.
Misunderstanding five: HTTPS sites must have exclusive IP addresses
Since IPv4 will be allocated, many people are concerned about this problem. There is no doubt that only one SSL certificate can be installed per IP address. However, if you use the Subdomain wildcard SSL certificate (wildcard SSL certificate, which costs about $125 per year), you can deploy multiple HTTPS subdomains on one IP address. For example, https://www.httpwatch.com and https://store.httpwatch.com share the same IP address.
In addition, UCC (Unified Communications Certificate, Unified Communications Certificate) supports a single certificate to match multiple sites simultaneously, which can be a completely different domain name. SNI (server name indicates, server named indication) allows multiple certificates to be installed on more than one domain name on an IP address. Server side, Apache and Nginx support this technology, IIS does not support, client, IE 7+, Firefox 2.0+, Chrome 6+, Safari 2.1+ and opera 8.0+ support.
Misunderstanding IV: To purchase a new certificate when transferring a server
Deploying an SSL certificate requires a few steps such as:
1. On your server, generate a CSR file (SSL certificate request file, SSL Certificate Signing requests).
2. Use the CSR file to purchase an SSL certificate.
3. Install the SSL certificate.
These steps are carefully designed to ensure the security of the transmission and to prevent anyone from intercepting or illegally obtaining a certificate. As a result, the certificate you obtained in the second step cannot be used on another server. If you need to do this, you must export the certificate in a different format.
For example, the practice of IIS is to generate a. pfx file that can be transferred and password-protected.
By passing this file on to another server, you will be able to continue using the original SSL certificate.
Misunderstanding three: HTTPS is too slow
Using HTTPS does not make your site faster (it is actually possible, see below), but there are some tricks that can greatly reduce the extra overhead.
First, as long as the text content is compressed, it reduces the CPU resources that are consumed by decoding. However, this overhead is trivial for modern CPUs.
Second, an HTTPS connection is required, requiring additional TCP round trips, so that some bytes are sent and received. However, as you can see, the number of new bytes is very small.
The first time you open a webpage, the HTTPS protocol is a bit slower than the HTTP protocol because of the time it takes to read and verify the SSL certificate. Below is a waterfall diagram of the time the HTTP Web page was opened.
After the same Web page uses the HTTPS protocol, the opening time becomes longer.
The part that establishes the connection is about 10% slower. However, once a valid HTTPS connection is established and the Web page is refreshed, there is little difference between the two protocols. First the HTTP protocol refresh performance:
Then the HTTPS protocol:
Some users may find that HTTPS is a bit 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.
Misunderstanding two: It's safe to have Https,cookie and query strings.
Although cookies and query strings cannot be read directly from HTTPS data, you still need to make their values unpredictable.
For example, there used to be a British bank that directly uses sequential numbers to denote session IDs:
Hackers can register an account, find this cookie, and see how this value is represented. Then, change the cookie to hijack the other person's session ID. As for query strings, they can also be leaked in a similar way.
Misunderstanding one: Only the login page is registered, HTTPS is required
This idea is common. People feel that HTTPS can protect the user's password, and it is not necessary. The new Firefox browser plugin, Firesheep, proves the idea is wrong. We can see that it's easy to hijack other people's session on Twitter and Facebook.
The free wifi in the café is an ideal hijacking environment for two reasons:
1. This wifi is usually not encrypted, so it is easy to monitor all traffic.
2. WiFi typically uses NAT for both extranet and intranet address translation, and all intranet clients share an external network address. This means that the hijacked session looks much like the original login.
In Twitter, for example, its login page uses HTTPS, but after logging in, the other pages become HTTP. At this point, the session value in its cookie is exposed.
In other words, these cookies are created in an HTTPS environment, but they are transmitted in an HTTP environment. If someone has hijacked these cookies, then he can speak to you on Twitter as you are.
Original: http://blog.httpwatch.com/2011/01/28/top-7-myths-about-https/ Translation: http://www.ruanyifeng.com/blog/2011/02/seven_myths_about_https.html Translator: Nanyi
|