Thursday, August 02, 2012

Chrome 21 Fail

Web devs beware: the just-released Chrome 21 now blocks mixed content. If you're serving a https page that loads anything over http, that insecure load is now blocked silently (a warning message appears in the console but the user sees nothing).

I'm pretty sure this change was the culprit.

And I'm not seeing a setting that can modify this behavior either.

Wasted a couple hours today trying to figure out why all our pages were broken. Yes, yes, it would be nice if we could serve everything over https, but there are a few resources we rely on that we just can't.

Update: this only happens for javascript files, not images.

No comments: