Akamai... UGH. This company is horrible to deal with. My workplace is currently having a problem with them due to us using two different Internet connections. One is a state-owned pipe, and the other is thru AT&T. The AT&T pipe is our main line due to having 50x more bandwidth, but we use the public IP address of the backup pipe, as it used to be our main line for many years.

Apparently, this doesn't sit well with Akamai, and they decided to block traffic from our IP. Overnight, software updates and even Apple app downloads were throttled. Our IT director has had a fun time being redirected and reaching dead-ends trying to get this fixed. Akamai just doesn't seem interested in listening to their customers...

Akamai... UGH. This company is horrible to deal with. My workplace is currently having a problem with them due to us using two different Internet connections. One is a state-owned pipe, and the other is thru AT&T. The AT&T pipe is our main line due to having 50x more bandwidth, but we use the public IP address of the backup pipe, as it used to be our main line for many years.

Apparently, this doesn't sit well with Akamai, and they decided to block traffic from our IP. Overnight, software updates and even Apple app downloads were throttled. Our IT director has had a fun time being redirected and reaching dead-ends trying to get this fixed. Akamai just doesn't seem interested in listening to their customers...

From my previous understanding, Bing does not officially support https (hence the redirection to http://www.bing.com). I don't think this is a new behavior. Has anybody got https://www.bing.com to work before today?

Am I the only one that ceased to have any confidence in the ssl warnings long ago? I mean, so far it has been wrong so many times it isn't even funny, and I am not aware of it actually having been a valid warning for a MitM attack once so far.

Am I the only one that ceased to have any confidence in the ssl warnings long ago? I mean, so far it has been wrong so many times it isn't even funny, and I am not aware of it actually having been a valid warning for a MitM attack once so far.

The warnings have not been wrong, really. The certs and/or serving sites have been wrong, in one way or another. And that's a problem: as soon as users give up and just start clicking through, or as soon as we "train" people to click through frequently, even when it's safe, that's when the risks skyrocket.

Am I the only one that ceased to have any confidence in the ssl warnings long ago? I mean, so far it has been wrong so many times it isn't even funny, and I am not aware of it actually having been a valid warning for a MitM attack once so far.

Which do you think it more likely; an attacker is skilled enough to be in a position to launch a mitm attack, but not aware that the browser is going to raise holy hell when the certs are misconfigured.OrThe admin made a mistake?

The warnings aren't wrong... it's just there is no way to tell a real attack from a mistake on the part of the admin.

From my previous understanding, Bing does not officially support https (hence the redirection to http://www.bing.com). I don't think this is a new behavior. Has anybody got https://www.bing.com to work before today?

I work for Bing.

We do not currently support HTTPS searches and do redirect users coming in via HTTPS to HTTP.

Poetic justice. Hotmail, msn.com, and live.com (all owned by MS) have been randomly blocking e-mails sent via non-MS ISPs (e.g., Comcast, Godaddy, and XO) for at least ten years. The e-mail sources blocked by the Microsoft services are not on any other block lists. Microsoft acknowledges that the blocking is in error. But it often takes a long time to fix, despite MS's claim that there's an easy fix for the ISPs to implement. (For info, search the following string found in the bounce message: "Reasons for rejection may be related to content with spam-like characteristics".)

From my previous understanding, Bing does not officially support https (hence the redirection to http://www.bing.com). I don't think this is a new behavior. Has anybody got https://www.bing.com to work before today?

I work for Bing.

We do not currently support HTTPS searches and do redirect users coming in via HTTPS to HTTP.

Would be handy if you guys supported something as basic as that. Might want to get on that. After you update your certificate, of course.

From my previous understanding, Bing does not officially support https (hence the redirection to http://www.bing.com). I don't think this is a new behavior. Has anybody got https://www.bing.com to work before today?

I work for Bing.

We do not currently support HTTPS searches and do redirect users coming in via HTTPS to HTTP.

Would be handy if you guys supported something as basic as that. Might want to get on that. After you update your certificate, of course.

It's not their certificate. It's Akamai's. And I don't think that a search engine really needs https.