From: Justin Erenkrantz Date: Thu, 17 May 2007 18:17:23 +0000 (+0000) Subject: mod_disk_cache: If the Vary'd content is stale, we can handle it via our X-Git-Tag: 2.3.0~1805 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c795f75fea2166379ea41c961e56939e18b51901;p=apache mod_disk_cache: If the Vary'd content is stale, we can handle it via our freshness tests which will attempt to revalidate the content. * modules/cache/mod_disk_cache.c (open_entity): If the root Vary index is stale, we don't need to throw away potentially stale content - we can try to refresh it. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@539054 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/modules/cache/mod_disk_cache.c b/modules/cache/mod_disk_cache.c index f1a34d51e5..3d71eb8128 100644 --- a/modules/cache/mod_disk_cache.c +++ b/modules/cache/mod_disk_cache.c @@ -422,10 +422,6 @@ static int open_entity(cache_handle_t *h, request_rec *r, const char *key) len = sizeof(expire); apr_file_read_full(dobj->hfd, &expire, len, &len); - if (expire < r->request_time) { - return DECLINED; - } - varray = apr_array_make(r->pool, 5, sizeof(char*)); rc = read_array(r, varray, dobj->hfd); if (rc != APR_SUCCESS) {