Closed
Bug 289847
Opened 19 years ago
Closed 19 years ago
Closing the "Security Warning" will not prevent a secure site from loading.
Categories
(Firefox :: Security, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: godsfantasy, Assigned: dveditz)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 When one visit a secure site, the "Security Warning" would come up. However, when you close that warning by pressing the 'X' on the top right of its Window, Firefox will proceed to load the website. In other words, there is no way of stopping the secure website from loading. Firefox 1.0.2 on Windows XP SP2 w/ Java 1.5 Update 2 Reproducible: Always Steps to Reproduce: 1. Go to http://www.paypal.com 2. Click on "Log in" on the top right 3. Security Warning comes up. Close it by pressing 'X' on the top right of the dialogue box. Actual Results: Firefox 1.0.2 proceed to load the website (in this case, Paypal's login page). Expected Results: Firefix 1.0.2 should NOT have proceeded loading the webpage (in this case, Paypal's login page). Windows XP SP2 w/ all latest patch installed Java 1.5 Update 2 Firefox 1.0.2 (public release)
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Comment 3•12 years ago
|
||
HTTPS Mixed Content: Loading a web page with mixed content will generate a warning, but there doesn't seem to be a way to prevent the HTTP content to be loaded. Following an "http://" link from an HTTPS page: this generates a warning (with security.warn_leaving_secure set to true), but still does it anyway. It would be better if there was a way to cancel the action (similar to the way it happens when submitting a form on an HTTPS page to a plain HTTP target).
Comment 4•12 years ago
|
||
Both of those dialog boxes were recently completely removed in bug 799009.
Comment 5•12 years ago
|
||
It's not just about the warning boxes, but about the ability to prevent the insecure action from happening. You say in bug 799009: > 4. Warning, you are viewing a site with mixed content. > > For #4, we've already decided to use passive indicators for mixed content, instead of active indicators. Having passive indicators can make sense (as long as they're still clearly visible, see bug 804974, crossing part of the bar with a red line is a good example). However, there should still be another box asking whether the user wants to proceed, or having a way to prevent the browser from making the request. I guess this falls under bug 782654.
You need to log in
before you can comment on or make changes to this bug.
Description
•