Closed
Bug 779317
Opened 12 years ago
Closed 11 years ago
Allow initializing safe browsing's key manager without fetching a key
Categories
(Toolkit :: Safe Browsing, defect)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
DUPLICATE
of bug 783047
People
(Reporter: Dolske, Unassigned)
Details
Currently the Safe Browsing code has to jump through a few hoops to avoid setting the "keyUrl" used by the backend's key manager. It does this because apparently just the act of setting the URL results in a key being fetched from the URL, which would be unwanted if the user has disabled Safe Browsing.
This really ought to all be handled behind the scenes... We should be able to set the URL without triggering a fetch. Rather, the fetch should just be triggered on-demand if it's not available when an update is performed.
Comment 1•11 years ago
|
||
This will be fixed by the HTTPS switch, which does away with all the key-juggling.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•11 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•