It's not just Bing. I'm always accidentally going to http://stackoverflow.com & getting an error.
I don't understand - that's never resulted in an error for me.
Bing doesn't support SSL
51–60 of 163 posts
Re: Bing doesn't support SSL
#52It's not just Bing. I'm always accidentally going to http://stackoverflow.com & getting an error.
Shh, only MS bashing can go on in this thread
Re: Bing doesn't support SSL
#53Earlier quoted context omitted.
I couldn't find something on google, so I decided to give it a try. Can't hurt. I wanted to find out if anyone has done a study on language confusion(the effect where Russians have a hard time getting good at Polish because they confuse Polish words with Russian ones). Still can't find it ;)
I know about funny word differences, but we have no problems learning russian, why russians would have problems learning polish? this is my favorite http://translate.google.com/#ru/pl/%D0%BA%D0%BE%D0%B2%D0%B5%... (in polish it sounds like 'caviar in a can')
Well, I know neither Polish nor Russian, but here in Prague I know a lot of Russians that never learn to say the word dobrý. They say dobry(short y) instead, which exists in Russian. They never learn to say it long, even when you point it out to them.
Re: Bing doesn't support SSL
#54The real question is, is bing.com even supposed to be served over https?
Re: Bing doesn't support SSL
#55I've gotten a certificate error for over a year with Bing on HTTPS. I always just assumed that they, somewhat surprisingly, just didn't support HTTPS yet.
Re: Bing doesn't support SSL
#56Wow. This has been going on for an hour now. It's such a simple fix, especially since one would assume that they already have a valid cert somewhere (or that Akamai does). Yet they've had an hour of SSL downtime. Does anyone know if Bing has any SSL-only clients? Like do any of their toolbars or built-in search widgets in Windows use SSL by default?
Re: Bing doesn't support SSL
#57This is the second major flub this year. Azure's cert expired in prod not many weeks ago.
Well, it is not really a flub of this year. Or even something specific to Bing (try https://www.nba.com/ or https://www.jetstar.com/ ) Basically Akamai is using the same ssl certifate on (most?) of its edge servers. The reason for that is that traditionally it is difficult to decide for a server that is serving multiple domains, which SSL certificate to show for a client -- the HTTP header, which contains the hostnam…
Akamai definitely supports custom SSL certs. You provide them a chain cert and they pass it on your behalf.
To me, this looks like they pushed the wrong cert to prod.
Re: Bing doesn't support SSL
#58This is the second major flub this year. Azure's cert expired in prod not many weeks ago.
Well, it is not really a flub of this year. Or even something specific to Bing (try https://www.nba.com/ or https://www.jetstar.com/ ) Basically Akamai is using the same ssl certifate on (most?) of its edge servers. The reason for that is that traditionally it is difficult to decide for a server that is serving multiple domains, which SSL certificate to show for a client -- the HTTP header, which contains the hostnam…
Akamai isn't using the same certificate on its edge servers, unless you mean the same customer certificate being replicated (in which case you are correct). Basically, Akamai maps each ssl certificate to a slot on the cache server, which is assigned to a map similar to the standard edge CDN. Each edge machine thinks itself the site. Each time a new certificate is issued by an Akamai partner CA or the customer's CA of choice, it is pushed out by Akamai to the ssl edge network.
SAN certs are an entirely different ball of wax. Akamai does support them, but there are some challenges getting them deployed.
Unfortunately, the deployment for any type of certificate with Akamai is a very manual process.
Re: Bing doesn't support SSL
#59Slightly off-topic: what's a good way to handle cases such as this where you have a wildcard certificate?
I'll be getting a wildcard certificate for a project and, never having used one before, I had assumed the certificate would be valid for an entire domain.
I understand from this situation that a wildcard certificate is relevant only to https://*.example.com and not the subdomainless https://example.com.
Assuming that to be the case, is having a wildcard certificate for *.example.com and a second certificate for example.com the solution? It'd be nice to have the entire domain covered by a wildcard certificate and not just all subdomains.
Re: Bing doesn't support SSL
#60TL;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
We were experiencing a similar issue with a third party analytics solution where their SSL cert all of the sudden started to be delivered by Akamai as opposed to the FQDN of the company, as it was before. I am curious if Akamai is at fault here?