Last Comment Bug 91532 - Need offline cache in OCSP code.
: Need offline cache in OCSP code.
Status: RESOLVED DUPLICATE of bug 48597
Product: NSS
Classification: Components
Component: Libraries (show other bugs)
: 3.2.1
: All All
P2 enhancement (vote)
: 4.0
Assigned To: Julien Pierre
: Bishakha Banerjee
Depends on:
  Show dependency treegraph
Reported: 2001-07-19 14:19 PDT by Javier Delgadillo
Modified: 2004-02-13 00:23 PST (History)
4 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Javier Delgadillo 2001-07-19 14:19:14 PDT
Customers have asked for PSM to provide an off-line cache of OCSP responses. 
PSM can't do that until NSS provides caching of OCSP responses.
Comment 1 User image Wan-Teh Chang 2001-10-31 19:24:33 PST
Assigned the RFE to Julien.
Comment 2 User image Wan-Teh Chang 2002-04-25 16:34:16 PDT
Changed the QA contact to Bishakha.
Comment 3 User image Torben 2002-10-24 07:55:41 PDT
Dupe of bug 48597?
Comment 4 User image Wan-Teh Chang 2002-10-24 10:32:57 PDT
Bug 48597 is not a duplicate of this bug but
rather a PSM bug that depends on this NSS bug.
Comment 5 User image Wan-Teh Chang 2003-05-12 14:48:06 PDT
An offline cache requires storing the OCSP responses in
persistent storage.  The design and implementation of
the persistence is complicated.  A simpler OCSP cache
that can't be used offline or across application sessions
is still useful because it could improve performance by
reducing the number of OCSP responses that need to go
to the network.  At the NSS OCSP meeting on May 1, we
decided that the simpler, non-offline OCSP cache could
be implemented first, and so it has been filed as bug
Comment 6 User image Julien Pierre 2003-09-29 17:25:13 PDT
FYI, the offline cache could use code from the simpler online cache, so I'm
adding a dependency to bug 205406.
Comment 7 User image Nelson Bolyard (seldom reads bugmail) 2004-02-13 00:23:15 PST
This bug is simply a dupe of 48597.  

*** This bug has been marked as a duplicate of 48597 ***

Note You need to log in before you can comment on or make changes to this bug.