Some CRL files are very large and not updated very often. It would make sense to use the If-Modified-Since header when retrieving files over HTTP to determine if the CRL has changed since the last retrieval.
Created attachment 156133 [details] Patch to include If-Modified-Since and handle that response I have to trick the CRL manager into accepting a 0-length response in this case. Normally we would consider that an error.
Created attachment 156225 [details] Updated patch This updated patch includes: - Separate logging for a 304. It isn't really an "error" when this occurs and it could alarm and confuse people - Added a ChangeLog
Checking in ChangeLog; /cvs/dirsec/mod_revocator/ChangeLog,v <-- ChangeLog new revision: 1.2; previous revision: 1.1 done Checking in client.cpp; /cvs/dirsec/mod_revocator/client.cpp,v <-- client.cpp new revision: 1.3; previous revision: 1.2 done Checking in client.h; /cvs/dirsec/mod_revocator/client.h,v <-- client.h new revision: 1.3; previous revision: 1.2 done Checking in client_err.h; /cvs/dirsec/mod_revocator/client_err.h,v <-- client_err.h new revision: 1.3; previous revision: 1.2 done Checking in crlmanager.cpp; /cvs/dirsec/mod_revocator/crlmanager.cpp,v <-- crlmanager.cpp new revision: 1.3; previous revision: 1.2 done Checking in http-client.cpp; /cvs/dirsec/mod_revocator/http-client.cpp,v <-- http-client.cpp new revision: 1.4; previous revision: 1.3 done Checking in mod_rev.c; /cvs/dirsec/mod_revocator/mod_rev.c,v <-- mod_rev.c new revision: 1.4; previous revision: 1.3 done Checking in reverror.h; /cvs/dirsec/mod_revocator/reverror.h,v <-- reverror.h new revision: 1.3; previous revision: 1.2 done Running syncmail... Mailing relnotes... ...syncmail done. Running syncmail... Mailing cvsdirsec.com... ...syncmail done.