Closed Bug 482660 Opened 16 years ago Closed 16 years ago

Add-Cert-Exception dialog broken for unknown-issuer sites

Categories

(Core :: Security: PSM, defect)

1.9.1 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: KaiE, Assigned: KaiE)

References

()

Details

(Keywords: regression)

Found this while trying to understand bug 470240... Tested https://sial.org/ but same problem also happens with https://www.cacert.org - connect to https://www.cacert.org - you'll get an error page - go to add exception - the dialog will automatically attempt to fetch the cert (did you change the default to auto-fetch in ff 3.1? I didn't notice that... anyway...) excepted behavior: dialog gets filled with site's cert information actual behavior: - cert error dialogs pops up (on top of add exception dialog) - click ok - no cert information is filled into the dialog - can not add an exception This is a regression, it worked fine in FF 3.0.x For comparison, other kind of cert errors still work with the FF 3.1 dialog, like the hostname mismatch for https://amazon.com
Flags: blocking1.9.1?
Keywords: regression
blocks 470240, can't triage that one, until this one is fixed
Blocks: 470240
Hmm - I do not see this behaviour. On both of your examples, loading the pages in a reasonably-recent build does the correct thing; add exception->dialog->cert fetch->confirm exception->load site works. Is this a recent regression, or is one of us doing something atypical?
Hmmm... testing with mochitestingprofile: When I go to https://www.cacert.org/ and wait for some time I experience bug 453442 - a cert error dialog pops up and I found out that it comes from favicon.ico request. I could reproduce it only ones... When I go to https://www.cacert.org/ and DON'T wait for the dialog, open the add-exception dialog, it gets, after a delay, automatically filled (quit strange, but it looks like a normal behavior...). When I click "Confirm security exception" all goes OK. Kai, it looks like you are experiencing bug 453442 or some kind of regression that is reproducible only under some special conditions. Fix to that bug was not in the security code but somewhere in the browser code.
WFM per comments, Kai, re-open if you can figure out why.
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: blocking1.9.1?
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.