Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 49782 invoked from network); 18 May 2007 11:51:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 May 2007 11:51:32 -0000 Received: (qmail 76924 invoked by uid 500); 18 May 2007 11:51:34 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 76837 invoked by uid 500); 18 May 2007 11:51:33 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 76822 invoked by uid 99); 18 May 2007 11:51:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2007 04:51:33 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 18 May 2007 04:51:27 -0700 Received: (qmail 49080 invoked by uid 2161); 18 May 2007 11:51:05 -0000 Received: from [192.168.2.4] (euler.heimnetz.de [192.168.2.4]) by cerberus.heimnetz.de (Postfix on SuSE Linux 7.0 (i386)) with ESMTP id 74F0A1721C for ; Fri, 18 May 2007 13:30:11 +0200 (CEST) Message-ID: <464D8E59.30507@apache.org> Date: Fri, 18 May 2007 13:30:33 +0200 From: Ruediger Pluem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060417 X-Accept-Language: de, en, de-de, en-gb, cy, zu, xh MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: Any progress on PR41230 (HEAD issues on cached items)? References: <5c902b9e0705171626l207f43a9lc2e9f86cdfaa5c1e@mail.gmail.com> <464CEA04.1050405@apache.org> <5c902b9e0705171723p75f33c14ta7909c400b6dbe0e@mail.gmail.com> In-Reply-To: <5c902b9e0705171723p75f33c14ta7909c400b6dbe0e@mail.gmail.com> X-Enigmail-Version: 0.90.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org On 05/18/2007 02:23 AM, Justin Erenkrantz wrote: > On 5/17/07, Ruediger Pluem wrote: > >> why. Also the entity is not physically removed from the cache if it is >> really stale. >> This does not matter in the non HEAD case as it gets overwritten by >> the fresh response, >> but in the HEAD case it should be physically removed IMO. > > > Well, because rv == !OK, wouldn't the CACHE_REMOVE_URL filter hit? > That should do the dirty deed, no? -- justin No, as the CACHE_REMOVE_URL filter will only work if there is a cache->handle or a cache->stale_handle. We have neither, as cache->stale_handle is set to NULL in the case that the cached entity is *really* stale and we do not create a new entity (and thus a cache->handle) in the HEAD case. Regards R�diger