Open Bug 625254 Opened 15 years ago Updated 4 years ago

HTTPS framesets do not display error page

Categories

(Firefox :: Security, defect)

defect

Tracking

()

People

(Reporter: u279076, Unassigned)

Details

(Whiteboard: [4b9])

https://litmus.mozilla.org/show_test.cgi?id=11331 Given the test case above, it appears as though HTTPS framesets should display a "Secure Connection Failed" error page. However, the test does not display this error page; it just loads the content. Can I get any feedback on whether this testcase is valid anymore? In other words, should HTTPS framesets continue to display an error page?
Whiteboard: [4b9]
Initial state: the frameset => no upper frame => no lower frame => no security state => no After I click "Link 1" in the upper frame: the frameset => no upper frame => secure lower frame => no security state => mixed After I click "Link 2" in the lower frame: the frameset => no upper frame => secure lower frame => no security state => mixed And, there is a comment: http://mxr.mozilla.org/mozilla-central/source/security/manager/boot/src/nsSecureBrowserUIImpl.cpp#1376 1376 // we'll treat "broken" exactly like "insecure", 1377 // i.e. we do not show alerts when switching between broken and insecure 1378 1379 /* 1380 from to shows alert 1381 ------------------------------ --------------- 1382 1383 no or broken -> no or broken => <NOTHING SHOWN> 1384 1385 no or broken -> mixed => mixed alert 1386 no or broken -> low => low alert 1387 no or broken -> high => high alert 1388 1389 mixed, high, low -> no, broken => leaving secure 1390 1391 mixed -> low => low alert 1392 mixed -> high => high alert 1393 1394 high -> low => low alert 1395 high -> mixed => mixed 1396 1397 low -> high => high 1398 low -> mixed => mixed The testcase seems to match to the case "no or broken -> mixed" and the expected result certainly seems "mixed alert".
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.