← Back to team overview

ubuntu-webapps-bugs team mailing list archive

[Bug 1503035] [NEW] If a certificate error is allowed, sub-resources are still blocked

 

Public bug reported:

If an application overrides a certificate error for a page, the page is
loaded with sub-resources blocked if those subresource loads are
affected by the same error with the same certificate. This behaviour is
different to both Chromium and Firefox.

What's missing in Oxide is that we need to remember the application
decision for a pre-determined amount of time, so that we can check this
decision in our implementation of content::SSLHostStateDelegate.

** Affects: oxide
     Importance: Medium
         Status: Triaged

** Changed in: oxide
   Importance: Undecided => Medium

** Changed in: oxide
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1503035

Title:
  If a certificate error is allowed, sub-resources are still blocked

Status in Oxide:
  Triaged

Bug description:
  If an application overrides a certificate error for a page, the page
  is loaded with sub-resources blocked if those subresource loads are
  affected by the same error with the same certificate. This behaviour
  is different to both Chromium and Firefox.

  What's missing in Oxide is that we need to remember the application
  decision for a pre-determined amount of time, so that we can check
  this decision in our implementation of content::SSLHostStateDelegate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1503035/+subscriptions