Earlier quoted context omitted.
Wow, that's the first time I've ever seen a 0-word article get the TL;DR treatment.
TL;DR means "here's a very short explanation".
Too Long; Didn't Read
151–160 of 163 posts
TL;DR: bing SSL certificate is wrong. https://bing.com : subject=/CN=*.bing.com https://www.bing.com : subject=/C=US/O=Akamai Technologies, Inc./CN=a248.e.akamai.net
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 into the address bar to generate this 'error'. Bing does support SSL on ssl.bing.com and publishes various links on that sub-domain, such as https://ssl.bing.com/webmaster/home/mysites The fact that the https://www.bing.com redirects to the HTTP version should be…
Earlier quoted context omitted.
...what kind of massage you received? My browser only talk about the warning, but i only have old chromium... Not auto-updating g chrome
All people giving downvotes to this comment, I think you are being unfair to this person who just seems to have a bad English. He probably meant "message".
Earlier quoted context omitted.
I don't think browsers should assume that http://blahblah and https://blahblah refer to the same resource.
Why not?
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.
Earlier quoted context omitted.
Very useful. It's not a super hard problem to solve, but I did think it provided enough value that companies would be willing to pay for it. SSL is used on the most important pieces of a business' infrastructure, I thought it'd be a simple sell. I also can't tell if certalert.me checks for hostname mismatches. That was another part of my service, because a misconfiguration is just as fatal as an expired certificate.
Out of curiosity.. how much money were you trying to charge for the service?
Earlier quoted context omitted.
I think it's as simple as having chosen an awful name. Bing is physically difficult to pronounce and it evokes no meaning whatsoever.
Do you really the pronunciation difficulty and lack of meaning is so significantly different than "Google" was when it launched? It's more vocalized, yes, but only a single syllable for Google's two, and relatively noone actually think of "googolplex" when talking about Google. The sound "bing", I think, conveys speediness, which they took advantage of with the slogan "Bing and decide". It's a quick, sharp sound - as…
When I first heard of the search engine google, I was immediately reminded of those childhood conversations about a number with 100 zeros following it. So yes, instant evocation. And maybe this would only happen with geeks, but that's exactly who they needed to convince to use their search engine.
Microsoft seems to have decided to ignore geeks and just markets directly to 'average users'. This to me seems like a very poor strategy. No smart people telling you to use Bing or Windows 8 and guess what...
Earlier quoted context omitted.
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 into the address bar to generate this 'error'. Bing does support SSL on ssl.bing.com and publishes various links on that sub-domain, such as https://ssl.bing.com/webmaster/home/mysites The fact that the https://www.bing.com redirects to the HTTP version should be…
The bing.com certificate says it is valid for the following names: ieonline.microsoft.com , .bing.com , .windowssearch.com. So why does https://www.bing.com not match *.bing.com?