Closed
Bug 114448
Opened 23 years ago
Closed 23 years ago
IN CRL autoupdate prefs window, should remove the menu for update from url
Categories
(Core Graveyard :: Security: UI, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
psm2.2
People
(Reporter: rangansen, Assigned: rangansen)
Details
Attachments
(1 file)
15.84 KB,
patch
|
KaiE
:
review+
hewitt
:
superreview+
|
Details | Diff | Splinter Review |
This menu is not relevant unless we support any more options other than the
'update from last fetched url'
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Updated•23 years ago
|
Priority: -- → P1
Target Milestone: --- → 2.2
Assignee | ||
Comment 2•23 years ago
|
||
Removed the idea of advertised url altogether - untill we have support for the
same in NSS. So, urlType also goes away from prefs. Its always last fetch url.
Assignee | ||
Comment 3•23 years ago
|
||
Kai, Please review ...
Comment 4•23 years ago
|
||
Patch looks good, but one question: Why do you store the preference, when there
is only one possible setting? Should we remove that code, too?
Assignee | ||
Comment 5•23 years ago
|
||
Do you mean the storing the url string? [The url type is not being stored
any amore]Because the autoupdate scheduler
[nsNSSComponent::getParamsForNextCrlToDownload ]checks for which crl to update
next, and then tries to import the crl directly from the corresp stored url
string. This operation is much less costly than looking up for the crl in the
db, and and finding out the lastfetchurl String
Comment 6•23 years ago
|
||
Comment on attachment 61138 [details] [diff] [review]
patch
I thought you were storing a flag whether you do "last fetch" or "as
advertised".
r=kaie
Attachment #61138 -
Flags: review+
Comment 7•23 years ago
|
||
Comment on attachment 61138 [details] [diff] [review]
patch
sr=hewitt
Attachment #61138 -
Flags: superreview+
Assignee | ||
Comment 8•23 years ago
|
||
Patch checked in ...
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•