Loading
Bug 26456: HTTP .onion sites inherit previous page's
certificate information A side-effect of marking the state of HTTP onion pages as 'secure' is that they go through the EvaluateAndUpdateSecurityState code path in nsSecureBrowserUIImpl. The previous implementation would just leave the SSLStatus as-is when receiving an SSL 'info' object which could not be QueryInterface'd to an nsISSLStatusProvider. For secure SSL pages, this code-path would never occur, but for secure onion pages it would. This would result in the previous page's SSLStatus hanging around when transitioning to an HTTP onion site with the previous HTTPS's SSL info remaining for the JavaScript chrome to pull in and display. This patch tweaks the EvaluateAndUpdateSecurityState to correctly clear the nsSecureBrowserUIImpl's owned nsISSLStatusProvider object in this scenario.