RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1390359 - foward port NSS OCSP cache settings
Summary: foward port NSS OCSP cache settings
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mod_nss
Version: 6.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Matthew Harmsen
QA Contact: Kaleem
Depends On:
Blocks: 1392582
TreeView+ depends on / blocked
Reported: 2016-10-31 19:48 UTC by Robert Bost
Modified: 2020-05-14 15:22 UTC (History)
6 users (show)

Fixed In Version: mod_nss-1.0.10-9.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
A regression was discovered in mod_nss-1.0.10, as it was forgotten to forward port 'NSS OCSP cache settings' logic from mod_nss-1.0.8. This bug fixes this issue. Utilization of this feature is described in comment 8 of this bug. [BZ #1390359]
Clone Of:
: 1392582 (view as bug list)
Last Closed: 2017-03-21 09:07:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
nss.conf (924 bytes, text/plain)
2017-01-17 09:31 UTC, Abhijeet Kasurde
no flags Details
console.log (31.67 KB, text/plain)
2017-01-17 09:31 UTC, Abhijeet Kasurde
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0576 0 normal SHIPPED_LIVE mod_nss bug fix update 2017-03-21 12:23:29 UTC

Description Robert Bost 2016-10-31 19:48:27 UTC
Description of problem:
Some additions were made to Red Hat Certificate System which would be helpful in standard RHEL mod_nss.

Version-Release number of selected component (if applicable): mod_nss-1.0.10-6.el6

Additional info:
Original bug report for RHEL 5:

Comment 3 Robert Bost 2016-11-01 20:05:14 UTC
(In reply to Robert Bost from comment #0)
> Description of problem:
> Some additions were made to Red Hat Certificate System which would be
> helpful in standard RHEL mod_nss.

In addition to the first comment on this bug, customer is seeing OCSP responses being cached and disabling cache would be solution.

Comment 9 Abhijeet Kasurde 2017-01-17 09:31:29 UTC
Created attachment 1241651 [details]

Comment 10 Abhijeet Kasurde 2017-01-17 09:31:50 UTC
Created attachment 1241652 [details]

Comment 11 Abhijeet Kasurde 2017-01-17 09:33:39 UTC
Verified using mod_nss version :: 


Tested various values of 
- NSSOCSPMinCacheEntryDuration
- NSSOCSPMaxCacheEntryDuration
- NSSOCSPTimeout

Please find the attachment for console.log and mod_nss + httpd configuration file.

Marking BZ as verified.

Comment 15 errata-xmlrpc 2017-03-21 09:07:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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