You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2005/01/19 14:46:09 UTC

DO NOT REPLY [Bug 14104] - not documented: must restart server to load new CRL

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=14104>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=14104


jorton@redhat.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




------- Additional Comments From jorton@redhat.com  2005-01-19 14:46 -------
Periodically reloading the CRL file from within httpd does not really sound
feasible (would you re-load and reparse it in each child? what if the children
got out of synch? what if the re-load failed? what about thread-safety issues
since the CRL is stored in the server-global config structure).

If the CRL changes relatively infrequently over time, you could cron a
(graceful) restart to pick up changes.  If it is updated so frequently that
restarting to pick up changes is not practical, you need OCSP (or something like
it).

-> WONTFIX

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org