Open
Bug 1116976
Opened 10 years ago
Updated 2 years ago
uncaught exceptions can leave the certificate exception dialog box in an unusable state
Categories
(Core :: Security: PSM, defect, P3)
Tracking
()
NEW
People
(Reporter: s3445849, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [psm-backlog])
Attachments
(1 file)
|
(deleted),
image/png
|
Details |
Screenshot from 2015-01-02 00:12:55.png
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/38.0.2125.111 Chrome/38.0.2125.111 Safari/537.36
Steps to reproduce:
I try to enter a wrong address of a page "httpx://www.nytimes.com" and hit Get Certificate
Actual results:
The browser does not response or maybe it takes too long to response because I try to stay at the window for more than 1 hour but it keeps "Attempting to identify the site..." and freeze all buttons but Cancel.
Expected results:
This address is not valid so it should return a message show that the entered address is invalid.
|
Reporter | |
Updated•10 years ago
|
Summary: Firefox takes too long to response when attempting to add wrong security exception → Firefox takes too long to response when attempting to add wrong address on security exception
|
||
Comment 1•10 years ago
|
||
Reproduced (waiting for a couple of minutes) with 2015-01-03-03-02-15-mozilla-central-firefox-37.0a1.ru.linux-x86_64.
Component: Untriaged → Security: PSM
Product: Firefox → Core
Looks like what's going on is that code waits asynchronously on the result of the request. If there's an exception at the wrong time, that code will wait indefinitely.
Blocks: 1029832
Summary: Firefox takes too long to response when attempting to add wrong address on security exception → uncaught exceptions can leave the certificate exception dialog box in an unusable state
|
||
Updated•10 years ago
|
OS: Linux → All
Hardware: x86_64 → All
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [psm-backlog]
Priority: -- → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•