Closed
Bug 1346842
Opened 7 years ago
Closed 7 years ago
Certificate security exception dialog not working in view-source window
Categories
(Firefox :: Security, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 941354
People
(Reporter: premek.vysoky, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 Build ID: 20170125094131 Steps to reproduce: I tampered with hosts file to redirect some domains. Therefore a server b.com domain certificate wasn't valid, but I still want to access files there. This can be done using the "Confirm security exception" dialog. 1) Have a page at domain a.com 2) Page on a.com is referencing static files (CSS/JS) from b.com 3) Because b.com certificate is suspicious, it wouldn't load these static resources 4) I go to view source code and click on any CSS reference, such as b.com/css/main.css 5) This brings the certificate exception dialog before I can view this file. 6) Confirmation button in this dialog does not do anything. Actual results: Confirmation button in certificate security exception dialog does not do anything, when viewed inside view-source: window. Clicking "Get certificate" and then clicking this button does not help. Expected results: The dialog should have been confirmed, security exception allowed and CSS contents displayed.
STR: 1. Open the view-source:https://badssl.com/ 2. Click on link of <a href="https://expired.badssl.com/" class="bad"> 3. Try the add to confirm this security exception. Actual results: 01:43:37.880 NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.host] browser.js:3281 01:43:40.932 NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.port] exceptionDialog.js:159 in Browser Console.
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Component: Untriaged → Security
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → All
Looks like bug 941354.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•