Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 8155 invoked from network); 18 May 2007 00:23:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 May 2007 00:23:39 -0000 Received: (qmail 20314 invoked by uid 500); 18 May 2007 00:23:44 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 19420 invoked by uid 500); 18 May 2007 00:23:42 -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 19409 invoked by uid 99); 18 May 2007 00:23:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 May 2007 17:23:42 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of justin.erenkrantz@gmail.com designates 209.85.132.248 as permitted sender) Received: from [209.85.132.248] (HELO an-out-0708.google.com) (209.85.132.248) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 May 2007 17:23:35 -0700 Received: by an-out-0708.google.com with SMTP id d31so186017and for ; Thu, 17 May 2007 17:23:13 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=tk0I4+czkKhEHUjWdIi142K9gOnkM92dg+yAbaIwerorWH+A7+3sN84jaDiRbgMF+SFo9FhBOMUBHxNtiHMWFgRhoYoom7fRenAfKSYHfEvGlOaYt6t+70/UdkoYMAErEVbU4++Qmy1a2TRbCsYE1oFSxwhDEPijwWelnW8ACEw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=OZP2DJDYNpurrQk52t8hrUO9wsiP182rUIT5vUyx+aG07fqh9RuDgNl+8fmnwSt8FhG7KV/ky+AGLPhPJq0o6byVt+pBxhg2G8Q/FRZ1NKy8JVQvpiDZccVcjm3g8xMP3zl95169jOC96K01CZaBIfh1rpkMlqLAWk8Gh47zipY= Received: by 10.114.127.1 with SMTP id z1mr522754wac.1179447789214; Thu, 17 May 2007 17:23:09 -0700 (PDT) Received: by 10.114.197.5 with HTTP; Thu, 17 May 2007 17:23:09 -0700 (PDT) Message-ID: <5c902b9e0705171723p75f33c14ta7909c400b6dbe0e@mail.gmail.com> Date: Thu, 17 May 2007 17:23:09 -0700 From: "Justin Erenkrantz" Sender: justin.erenkrantz@gmail.com To: dev@httpd.apache.org Subject: Re: Any progress on PR41230 (HEAD issues on cached items)? In-Reply-To: <464CEA04.1050405@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5c902b9e0705171626l207f43a9lc2e9f86cdfaa5c1e@mail.gmail.com> <464CEA04.1050405@apache.org> X-Google-Sender-Auth: ddf07fe88d379b9d X-Virus-Checked: Checked by ClamAV on apache.org 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