News for hackers. Stuff that matters.
Re:AMP Is What HTML Should Have Been by puddintane on Thursday August 11, 2016 @11:18PM (#12273211)
Yikes looks like someone didn't setup SSL properly on the project's website (http redirects to https) https://www.ampproject.org/ it'd be nice to see some of the examples.

edit Google cache isn't loading everything - at least to my knowledge.

edit 2 Yay web-archive to the rescue!

http://web.archive.org/web/20160811220337/https://www.amppro...

Re:AMP Is What HTML Should Have Been by paulbakaus on Friday August 12, 2016 @07:14PM (#12279433)
AMP team member here. Not sure I understand the issue.

It's by design that our site is only available via HTTPS. Is there a good reason for why you can't consume the HTTPS version?

Re:AMP Is What HTML Should Have Been by puddintane on Saturday August 20, 2016 @11:28AM (#12326981)
I am not entirely sure, as a web developer I've never seen a certificate pass all SSL checkers yet chrome and firefox on my computer (up-to-date) won't load them. I pondered a MITM attack but it's literally the only site this happens on - not exactly sure what is causing the https to not load on my end.

edit All I get is "ERR_SSL_PROTOCOL_ERROR" - I'm pretty sure I tested this link out at work but I will again on Monday to verify it happens there (currently I'm tethered as well as vpn'd to PIA and I don't think my provider T-Mobile is doing anything to block this one ssl)