Comment 1 for bug 1355120

The browser (well, Oxide) is behaving correctly here by blocking the insecure content. There isn't an API to tell the browser the content has been blocked or provide a way for the user to override the error at the moment, but in any case this is a website bug

https://support.google.com/chrome/answer/1342714?hl=en