trend http: to https: : Java Glossary

I have noticed that websites are rapidly converting from plain HTTP (Hypertext Transfer Protocol): protocol to encrypted HTTPS (Hypertext Transfer Protocol over SSL (Secure Socket Layer)): protocol. Even sites without any confidential information are doing this. Why? Google lead this change. The problem was the US government was violating its own laws and was spying on all traffic on the Internet both domestic and foreign. By law, they need to get a court order or a subpoena. Google is effectively flooding the net with encrypted decoys. The US government presumably does not have the technology to routinely break all the encrypted messages.

Should you too flip to https:?

• Google is pushing it. They will bump up your search engine rankings if you do.
• Google wants it universal to make life awkward for the snoops. The snoops can go on a goose chase decrypting pudding recipes.
• HTTPS: is a more robust protocol.
• You might be able to offset the overhead of HTTPS: by using SPDY (Speedy) which adds compaction.
• You do your part to make the government obey its own laws.

• HTTPS: adds overhead both in the amount of traffic, CPU (Central Processing Unit) used and time to get the session started.
• HTTPS: derails caching, except inside the browser. This means slower response times.
• You cannot use Wireshark to debug communications.
• Compression is impossible in https communications unless it is done by software in the end points.
• You must buy and install an SSL (Secure Sockets Layer) certificate on your server and renew it each year.