Closed
Bug 1182766
Opened 9 years ago
Closed 9 years ago
Ensure that when updates and gethash are unresponsive, the client doesn't stall
Categories
(Toolkit :: Safe Browsing, defect)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: francois, Unassigned)
References
Details
Attachments
(1 file)
|
(deleted),
application/x-javascript
|
Details |
When the local Safe Browsing database contains stale data (for example if updates aren't working because the server is down) we can use gethash to verify whether or not it's still valid.
What happens when gethash doesn't respond either? Do we stall? Do we have a very long timeout?
This investigation is related to bug 1032393.
|
Reporter | |
Comment 1•9 years ago
|
||
The fact that gethash is unresponsive or returns an error doesn't appear to affect the client.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•