7 ms·
>TL;DR: Bing doesn't support SSL on www.bing.com and has never publicized it as a supported feature. The submitter had to manually type https://www.bing.com htt
by TazeTSchnitzel 14y ago
>TL;DR: Bing doesn't support SSL on www.bing.com and has never publicized it as a supported feature. The submitter had to manually type https://www.bing.com https://www.bing.com into the address bar to generate this 'error'.
Or use HTTPS Everywhere. Personally, I'd also like it if in future, web browsers would try HTTPS first and HTTP second.
- deleted 14y ago[deleted]
- decklin 14y agohttp://en.wikipedia.org/wiki/Server_Name_Indication#Support http://en.wikipedia.org/wiki/Server_Name_Indication#Support
- wiml 14y agoI don't think browsers should assume that http://blahblah http://blahblah and https://blahblah https://blahblah refer to the same resource.
- ricardobeat 14y agoWhy not?
- gcr 14y agoBecause it's up to the individual website administrator to ensure he published them both the same way. I can construct a web server that sends version A of a site over normal HTTP, and version B of that same site over HTTPS. In fact, sometimes I do that by accident. :) It's a bad assumption.