This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
If for some reason you try to access the site with SSL (e.g. http://docs.webplatform.org/wiki/WPD:Getting_Started), you get a scary warning in Chrome about not reaching the server you thought you were. We never direct people to use HTTPS, so this would only show up if someone manually typed the 's' in the URL themselves.
It looks like to me this is due to Fastly offering SSL connections itself. So it is being identified as them, but our domain which is causing the message. I will see if Ryan Lane can look and see if there is an option for turning SSL off completely at Fastly's end. If he can't then I don't think there is anything we can do about this.