![\"codecrunch_chrome_kill_http\"](\"http:\/\/codecrunch.co\/blog\/wp-content\/uploads\/2016\/09\/codecrunch_chrome_kill_http-300x118.png\")
<\/p>\nGoogle recently announced that from January 2017 onwards chrome browser will start warning users about websites using insecure HTTP connections to transmit passwords and credit card data as insecure, as part of a long-term plan to mark all HTTP sites as non-secure.<\/p>\n
Eventually, Chrome will add the security warning to HTTP pages when a user visits them in the browser\u2019s \u201cIncognito\u201d mode, and later the warning will roll out to all HTTP pages.<\/p>\n
In January, Chrome users can start looking out for the security warning in the address bar of their browser. It\u2019ll look like this at first:<\/p>\n
<\/p>\n
![\"codecrunch_chrome_kill_http_for_https\"](\"http:\/\/codecrunch.co\/blog\/wp-content\/uploads\/2016\/09\/codecrunch_chrome_kill_http_for_https-300x146.png\")
<\/p>\n
Chrome currently indicates HTTP connections with a neutral indicator. This doesn\u2019t reflect the true lack of security for HTTP connections. When you load a website over HTTP, someone else on the network can look at or modify the site before it gets to you.<\/p>\n
The changes seem intended to pressure site owners\u00a0to switch to a more secure HTTPS, which encrypts data while in transit and helps prevent the site from being modified by a malicious user on the network. \u201cDon\u2019t wait to get started moving to HTTPS. HTTPS is easier and cheaper than ever before<\/a>, and enables both the best<\/a> performance<\/a> the web offers and\u00a0powerful<\/a> new<\/a> features<\/a> that are too sensitive for HTTP,\u201d Chrome\u2019s Emily Schechter wrote in a post announcing the changes.<\/p>\n Google, which runs Chrome, isn\u2019t the only company leaning on websites to make their connections more secure. Apple said earlier this year that it would require app developers to force HTTPS connections for iOS apps by the end of 2016, and Facebook\u2019s Instant Articles are served over HTTPS, automatically adding security for readers even if they wouldn\u2019t get it on the publication\u2019s own website. Pressure from some of the world\u2019s biggest tech companies will undoubtedly push security forward for millions of people.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Google recently announced that from January 2017 onwards chrome browser will start warning users about websites using insecure HTTP connections to transmit passwords and credit card data as insecure, as part of a long-term plan to mark all HTTP sites… Continue Reading →<\/a><\/p>\n","protected":false},"author":1,"featured_media":146,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,13],"tags":[65,60,62,66,61,63,64],"_links":{"self":[{"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/posts\/138"}],"collection":[{"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/comments?post=138"}],"version-history":[{"count":4,"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/posts\/138\/revisions"}],"predecessor-version":[{"id":144,"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/posts\/138\/revisions\/144"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/media\/146"}],"wp:attachment":[{"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/media?parent=138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/categories?post=138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/codecrunch.co\/blog\/wp-json\/wp\/v2\/tags?post=138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}