4 ms·
https://mobiforge.com/news-comment/no-https-then-bye-bye-geolocation-in-chrome-50 https://mobiforge.com/news-comment/no-https-then-bye-bye-geo... https://www.w
by pixl97 10y ago
https://mobiforge.com/news-comment/no-https-then-bye-bye-geolocation-in-chrome-50 https://mobiforge.com/news-comment/no-https-then-bye-bye-geo...
https://www.wordfence.com/blog/2017/01/chrome-56-ssl-https-wordpress/ https://www.wordfence.com/blog/2017/01/chrome-56-ssl-https-w...
https://blog.mozilla.org/security/2015/04/30/deprecating-non-secure-http/ https://blog.mozilla.org/security/2015/04/30/deprecating-non...
http://stackoverflow.com/questions/32106849/getcurrentposition-and-watchposition-are-deprecated-on-insecure-origins http://stackoverflow.com/questions/32106849/getcurrentpositi...
https://konklone.com/post/were-deprecating-http-and-its-going-to-be-okay https://konklone.com/post/were-deprecating-http-and-its-goin...
http://forums.whirlpool.net.au/archive/2598616 http://forums.whirlpool.net.au/archive/2598616
Just some random places to start to see why the major web browsers are not going to spend any time on non-encrypted protocols. A lot of devs need to help themselves and move to encrypted to connections before they are forced at browser-point.