Comment 7 for bug 1523261

Thanks Laryllan for providing a test account/server, I’ve managed to reproduce the issue. When visiting the owncloud web interface, I am getting the self-signed certificate warning page as expected, and if I choose to proceed anyway, the page loads, but a lot of its subresources are not loading correctly.

I’m seeing e.g.:

GET https://*******.spdns.de/owncloud/core/css/mobile.css?v=xxxxxxx net::ERR_INSECURE_RESPONSE
GET https://*******.spdns.de/owncloud/core/vendor/jquery-ui/themes/base/jquery-ui.css?v=xxxxxxx net::ERR_INSECURE_RESPONSE
GET https://*******.spdns.de/owncloud/index.php/core/js/oc.js?v=xxxxxxx net::ERR_INSECURE_RESPONSE

…among many other errors, which in turn trigger errors like:

  Uncaught ReferenceError: jQuery is not defined
  Uncaught ReferenceError: OC is not defined

It looks like accepting the self-signed certificate doesn’t make oxide trust it for loading subresources. Need to investigate whether it’s a bug in oxide, or in the way webbrowser-app uses it.