padlock shows wrong security status when viewing a page with frames (secure and not secure)
VERIFIED
WONTFIX
Status
People
(Reporter: S2, Assigned: Stephane Saux)
Tracking
Firefox Tracking Flags
(Not tracked)
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:
|
||
Comment 1•16 years ago
|
||
-> 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
|
||
Updated•16 years ago
|
||
QA Contact: junruh → bmartin
|
|
||
Comment 2•15 years ago
|
||
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
Last Resolved: 15 years ago
Priority: -- → P3
Resolution: --- → WONTFIX
Version: unspecified → 2.4
|
||
Comment 4•15 years ago
|
||
*** Bug 224770 has been marked as a duplicate of this bug. ***
|
||
Updated•2 years ago
|
||
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•