Closed Bug 197443 Opened 22 years ago Closed 22 years ago

padlock shows wrong security status when viewing a page with frames (secure and not secure)

Categories

(Core Graveyard :: Security: UI, defect, P3)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
Windows XP
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX

People

(Reporter: simon.santoro, Assigned: ssaux)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 first of all, i saw bug 140837 (how can i link to it in a message?), and i think this is not related to it (but i can be wrong). go to a page with two frames, one is secure, and the other not. the padlock shows that the page is insecure (open lock), but in my opinion it should be the "mixed content" icon (am i wrong?). additionaly, rightclicking on the secure frame, and going to frame info, shows no security tab, even if the frame is secure. Reproducible: Always Steps to Reproduce:
-> PSM (Please don't file crypto bugs on security:general)
Assignee: mstoltz → ssaux
Component: Security: General → Client Library
Product: Browser → PSM
QA Contact: carosendahl → junruh
Version: Trunk → unspecified
QA Contact: junruh → bmartin
If you put this code on a secure server you will see a mixed lock icon. If you put it on an insecure server, you will see a broken lock icon. This is as designed. <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <title>Frame Test</title> <frameset COLS="50%,50%"> <frame SRC="https://www.verisign.com"> <frame SRC="http://www.verisign.com" NAME="home"> </frameset> </head> <body> </body> </html> Right clicking on a frame and viewing frame info does not show the security tab is as designed.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Priority: -- → P3
Resolution: --- → WONTFIX
Version: unspecified → 2.4
Verified.
Status: RESOLVED → VERIFIED
*** Bug 224770 has been marked as a duplicate of this bug. ***
Product: PSM → Core
Version: psm2.4 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.