User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 (Debian package 1.0-2) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 (Debian package 1.0-2) When connecting to https://localhost, which has an expired self-signed certificate, with FF1.0 I see a series of three warning dialogs. I suggest two improvements. First, the order of the buttons should be made consistent between the dialogs. Second, all of these problems could be described on a single dialog. The dialogs and button orders are: 1. Server Certificate Expired Ok Cancel Help 2. Web site certified by an unknown authority Help Cancel Ok 3. Security Error: Domain name mismatch Ok Cancel Help Internet Explorer 6 presents a single warning window as follows: Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate. ! The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority ! The security certificate has expired or is not yet valid. ! The name on the security certificate is invalid or does not match the name of the site. Do you want to proceed? Yes No View Certificate While you may feel that IE is not presenting enough information, I suggest that the idea of presenting a single dialog describing all of the problems at one go, and so requiring only a single click to continue, is a good one. "More Info..." buttons could be used if necessary. Regards, Phil. Reproducible: Always Steps to Reproduce:
*** Bug 261403 has been marked as a duplicate of this bug. ***
Checked this out in a current build (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050413 Firefox/1.0+) and it appears that the problem of inconsistent button order has been fixed.
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/
(In reply to comment #3) > This is an automated message, with ID "auto-resolve01". I do not currently have time to check if this has been resolved in a new build. As soon as I do have time I will investigate. However it seems to me that this is not the sort of thing that gets resolved "by chance". It could be recategorised as Enhancement, if you like.
We use now error pages instead of a dialog. I will go ahead and mark this wontfix