----- Original Message -----
From: "Sean Donelan via Outages" <outages@outages.org>
This is how Akamai has handled non-SSL customers for the last 15 years. It is the same error message, and the same action. You just noticed it.
If you use https for a non-SSL customer on Akamai, you will connect to a Akamai server using a "default" SSL certificate for all customers on port 443.
If you use https for a SSL customer on Akamai, you connect to different IP addresses listening for specific customers which return a customer specific SSL certificate.
Doesn't that interact rather badly with HTTPS-Anywhere? Or, more to the point, would it not already have done so to date, rather loudly? Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274