{"id":32014,"date":"2017-09-29T16:43:02","date_gmt":"2017-09-29T13:43:02","guid":{"rendered":"https:\/\/blog.superhosting.bg?p=32014"},"modified":"2022-06-02T17:41:29","modified_gmt":"2022-06-02T14:41:29","slug":"next-step-to-make-the-web-more-secure-and-autossl","status":"publish","type":"post","link":"https:\/\/blog.superhosting.bg\/en\/next-step-to-make-the-web-more-secure-and-autossl.html","title":{"rendered":"Google Takes the Next Step Towards a More Secure (HTTPS) Web, SuperHosting.BG Also Moves on With AutoSSL"},"content":{"rendered":"

Google\u2019s plan for a more secure web is still in progress as the key tool for its implementation is the Chrome Web Browser<\/a>. The next phase of marking HTTP as non-secure web element has already started. As of October 2017 Google Chrome v.62<\/a> will display a Not Secure<\/strong> warning message in front of all HTTP pages containing forms no matter if their purpose is logging in, comments, feedback or other. Until recently<\/a> this notification was displayed only for HTTP pages with password or credit card form fields.<\/p>\n

Chrome v.62 <\/strong>will display the Not Secure<\/strong> message in front of all HTTP pages with forms.<\/p>\n

\"Not<\/p>\n

Mozilla Firefox will do the same!<\/strong><\/h4>\n

Many big companies followed Google\u2019s steps towards the idea of HTTPS everywhere<\/a>. Mozilla also plans to drop the non-secure HTTP<\/a> in Firefox.<\/p>\n

Firefox v.51 will start displaying a crossed out lock in the address bar on all sites that don\u2019t use HTTPS and contain a login form.<\/p>\n

\"Not<\/p>\n

\"Not<\/p>\n

Firefox 52 will visibly display a warning message in the fields of a login form when a certain webpage loads via HTTP. A broken lock icon will also be loaded in the address bar.<\/p>\n

The Next Step for Chrome and Firefox<\/strong><\/h4>\n

Google and Mozilla announce one and the same goal in their plan to quit the non-secure HTTP \u2013 their browsers will soon start marking in red each page that doesn\u2019t use HTTPS no matter what its contents are.<\/p>\n

Firefox<\/strong> will display<\/a> the crossed out lock for every HTTP webpage.<\/p>\n

\"Not<\/p>\n

Google Chrome<\/strong> will display<\/a> a triangle in red, containing the Not Secure notification.<\/p>\n

\"Not<\/p>\n

Some users may not have paid much attention to an HTTP\u2019s URL, but from now on it will be much easier since its shining red appearance. This surely will make visitors uncomfortable and they might start avoiding such websites. Many HTTP websites will lose the trust and attention of their regular users, especially if they are online stores or handle sensitive data.<\/p>\n

Luckily this time has not come yet and all HTTP websites still have time to migrate to HTTPS (or HTTP\/2).<\/p>\n

HTTPS (+HTTP\/2)<\/strong><\/em>
\nIf you still have not migrated to HTTPS here are some benefits and reasons fair enough to convince you into finally doing it:<\/p>\n