Hi,
I was playing with OCSP Stapling in 2.3.6-alpha tonight, and I noticed
that in the common case path, we will always lock a global mutex.
I don't see why this is needed for the cache hit case that uses
non-SHM cache providers.
In fact, modssl_dispatch_ocsp_request, which is called on a cache
miss, already has a serialize_request, so I'm not sure why there is a
global mutex at all, even for cache updates.
It seems that inside stapling_mutex_{on,off} in ssl_util_stapling.c,
the global mutex should only be used if (mc->stapling_cache->flags &
AP_SOCACHE_FLAG_NOTMPSAFE) is true?
Thoughts?
Thanks,
Paul
