Akamai is not limiting HTTP origin servers, however. Akamai will no longer allow Akamaized SSL service to entities that Akamai has not identified as an authorized user of the Akamai SSL service. There are probably many other sites which unintentionally proxy SSL in this manner. Akamai just happens to be a very large instance. Any SSL Web server that transparently proxies arbitrary SSL connections by re-wrapping requests is vulnerable.
Browsers traditionally make all authentication decisions.
Because the Akamai hosts re-wrapped unauthentic, arbitrary content with an authentic Verisign certificate, the browser was unable to determine authenticity. Users should not assume that data signed by a site's certificate is necessarily data being provided by the operator of that site. They should instead consult other information provided by the site operator to determine whether the digital signature is intended to convey some specific meaning, or no meaning at all. Akamai caught in Net filtering crossfire. The information has been provided by Kevin Fu .