Closed Bug 457021 Opened 11 years ago Closed 4 years ago

SSL error displays a dialog, not error page


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

1.9.0 Branch
Not set


(Not tracked)



(Reporter: nelson, Unassigned)




(Keywords: regression, Whiteboard: [psm-cert-errors])


(1 file)

Attached image screen shot of dialog
Using SM trunk nightly Gecko/20080922002657
when I visit a site with a cert from an unknown issuer, such as
I expect to get the SSL/certificate error page with the link/button for 
adding a security exception, not a security dialog.
But starting with this build, I get a security dialog that tells me
about the problem, and lets me view the cert or cancel, but nothing else.  

This dialog pops up modal to the window, so that even if I've switched 
to another tab, I cannot do anything in that tab until I have dismissed 
the dialog. :(

This is a pretty major functional regression.  Let's go back to the error
Summary: SSL error dislpay dialog, not error page → SSL error displays a dialog, not error page
I can reproduce with firefox trunk.

Occasionally I get both the error page and the dialog, but more often only the dialog. That's a regression. I don't what caused it.
Keywords: regression
Flags: blocking1.9.1?
OS: Windows XP → All
Hardware: PC → All
And it seems to be happening more often, recently.  I suspect at least part of it is related to bug 431712, but it's not clear if fixing that bug (which seems to be favicon-service-related?) would fix all occurrences.  Kai, anything land recently that would be a likely culprit?
The day I filed this bug, SM always used the dialog and not the page.
Today, using the same browser build and the same URL, I get the page 
and not the dialog.  I'm not saying the problem is gone, but only that
it is unpredictable.
Duplicate of this bug: 463028
When it's a regression we need the regression range. I'll try to get it within the next days.
Doesn't happen all the time, minor inconvenience, doesn't block. Should fix, if we can get a regression window.
Flags: blocking1.9.1? → blocking1.9.1-
Since my last comment I wasn't able to see this issue again. So no way for now to search for a regression range.
Duplicate of this bug: 476014
In bug 476014 it was a 100% repro on a clean install.  I used a vm so I know it is clean every install.  As you can see from the SS on that bug, it doesn't even get the view cert button so it makes it completely unusable without using a 3rd party tool to download the cert to manually accept it.

The problem site mentioned in this bug (457021) does not cause problems for me.  Following the repro in 476014 still does 100% of the time.

Sorry I can't put a prebuilt server with a cert with the problem up somewhere but none of the servers I have access to are visible to the outside.
this is still valid using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090315 Minefield/3.2a1pre ID:20090315050013 and reproduceable if you press ctrl+f5 rapidly (aka "hammer") like 20-40 times.

let's see if i can find a range ...
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008041107 Minefield/3.0pre ID:2008041107
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008041206 Minefield/3.0pre ID:2008041206

it's quite easy to reproduce if you set given url as homepage.

=> range:

my guess: bug 420187, bug 383369 or bug 358438
Kaie, could you check those three bugs? You provided the patches to all of them. Thanks.
I can reproduce:

- go to (cert error page)
- press ctrl+f5 many times quickly
- dialog comes up
Assignee: kaie → nobody
Whiteboard: [psm-cert-errors]
Can anyone still reproduce this?

At the very least, the STR from comment 13 doesn't result in a dialog for me
on a Win7 Aurora/FDE build, or a local Linux 64 m-i build.
I'm going to interpret the lack of responses to mean that this is no longer reproducable.

If it is still reproducable, feel free to re-open.
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.