https://issues.apache.org/bugzilla/show_bug.cgi?id=57121
--- Comment #1 from Jeff Trawick <[email protected]> --- SSLStaplingStandardCacheTimeout directly controls cache expiration, so once the 3600 seconds elapses the old response is no longer available. Thus, the previous response can't be used as a fallback if the responder can't be reached after the timeout expires. SSLStaplingResponseMaxAge is a final sanity check on a response, so it doesn't help here. Ideally a response would be refreshed well before cache expiration, without blocking other threads (which continue to use the previously cached response), and without removing a valid entry from the cache if a temporary communication error occurs. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
