Meta is using non-SSL endpoints for some resources and it breaks the site in Chrome

Question

For a few days now this has been a problem for me. I can no longer vote posts up or down on any meta channel from Chrome (Version 42.0.2311.152 (64-bit)) on OS X. Looking at the JavaScript console while trying to vote, it appears that Chrome is blocking a URI call because it's being made over a non-SSL end point:

The blocked calls occurred when I pressed the up-vote button. I get similar blocked calls in Chrome when I try to add an image to a question or answer on a meta channel.

It's only a problem on the meta channel. The main sites are fine.

I had to post this from...shudder...Safari to attach the image to the post. :)

Edit: this is possibly a problem for me because I visit all Stack Exchange sites via their https URLs and the meta sites have invalid certificates. This is what I get trying to use https://apple.meta.stackexchange.com/ from Chrome:

If I come to the site via the non-encrypted endpoint it works fine in Chrome. Chrome really doesn't like when your site mixes https and http requests to its own domain (and rightly so).

Answer 1

Figured it out.

First: the certificate for meta.apple.stackexchange.com is definitely invalid. That is, ultimately, at the heart of my problem.

But the problem for me, in Chrome, was caused by my use of the HTTPS Everywhere Chrome extension. It was responsible for blocking the http calls to meta endpoints that were being made from an https meta page. Once I disable the extension for meta I could vote again.

This all, however, is just pointing a serious flaw in the use of https on the meta sites that needs to be fixed. I'll argue this stands as a bug.