Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 96616 invoked from network); 2 May 2006 18:12:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 May 2006 18:12:28 -0000 Received: (qmail 45779 invoked by uid 500); 2 May 2006 15:22:26 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 45478 invoked by uid 500); 2 May 2006 15:22:23 -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 45467 invoked by uid 99); 2 May 2006 15:22:23 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 May 2006 08:22:23 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of minfrin@sharp.fm designates 64.49.220.200 as permitted sender) Received: from [64.49.220.200] (HELO chandler.sharp.fm) (64.49.220.200) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 May 2006 08:22:21 -0700 Received: from chandler.sharp.fm (localhost [127.0.0.1]) by chandler.sharp.fm (Postfix) with ESMTP id 13D8CE45A9; Tue, 2 May 2006 10:22:01 -0500 (CDT) Received: from www.sharp.fm (unknown [209.61.173.189]) by chandler.sharp.fm (Postfix) with ESMTP id E50A2E4396; Tue, 2 May 2006 10:22:00 -0500 (CDT) Received: from 196.8.104.37 (SquirrelMail authenticated user minfrin@sharp.fm); by www.sharp.fm with HTTP; Tue, 2 May 2006 17:22:00 +0200 (SAST) Message-ID: <11424.196.8.104.37.1146583320.squirrel@www.sharp.fm> In-Reply-To: <20060502140617.1f1d7550.davi@haxent.com.br> References: <4450CF63.2060305@turner.com><445136CC.6030305@sharp.fm><44520B45.6070507@turner.com><4455203F.9000509@sharp.fm><44560316.3030705@turner.com><445664B1.5030905@sharp.fm><445665B2.3010604@turner.com><445673B4.2000803@sharp.fm><44575D75.1060105@turner.com><60780.196.8.104.37.1146577230.squirrel@www.sharp.fm> <20060502140617.1f1d7550.davi@haxent.com.br> Date: Tue, 2 May 2006 17:22:00 +0200 (SAST) Subject: Re: Possible new cache architecture From: "Graham Leggett" To: dev@httpd.apache.org Cc: dev@httpd.apache.org, minfrin@sharp.fm User-Agent: SquirrelMail/1.4.3a-12.EL4 X-Mailer: SquirrelMail/1.4.3a-12.EL4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: ClamAV using ClamSMTP X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Tue, May 2, 2006 7:06 pm, Davi Arnaut said: > There is not such scenario. I will simulate a request using the disk_cache > format: The way HTTP caching works is a lot more complex than in your example, you haven't taken into account conditional HTTP requests. A typical conditional scenario goes like this: - Browser asks for URL from httpd. - Mod_cache has a cached copy by looking up the headers BUT - it's stale. mod_cache converts the browser's original request to a conditional request by adding the header If-None-Match. - The backend server answers "no worries, what you have is still fresh" by sending a "304 Not Modified". - mod_cache takes the headers from the 304, and replaces the headers on the cached entry, in the process making the entry "fresh" again. - mod_cache hands the cached data back to the browser. Read http://www.ietf.org/rfc/rfc2616.txt section 13 (mainly) to see in detail how this works. Regards, Graham --