Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 19292 invoked from network); 7 Feb 2008 09:02:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2008 09:02:30 -0000 Received: (qmail 14836 invoked by uid 500); 7 Feb 2008 09:02:09 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 14821 invoked by uid 500); 7 Feb 2008 09:02:09 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 14810 invoked by uid 99); 7 Feb 2008 09:02:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 01:02:09 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mutant.nz@gmail.com designates 72.14.246.241 as permitted sender) Received: from [72.14.246.241] (HELO ag-out-0708.google.com) (72.14.246.241) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 09:01:39 +0000 Received: by ag-out-0708.google.com with SMTP id 31so7718067agc.0 for ; Thu, 07 Feb 2008 01:01:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=s8mWVJik44VLft4mqTg/xCj3UfVSKrKwkMx37Gvxofk=; b=nwkdLWI5nTHgSaqR0vDVLTtP/Cv+LnUgebpl9LQxsUQbV4TycuU8Aca/gVhTEyD5r6Ytfjlo5LtHrrV0dhB9FX3jdBZGCbtKOYoMP8awmXSxwQ8YfXGCfjA11BXSvDtOfdwry27LVRA4t4Sao4g2JpM512+zoDiWlpFvWLAdOZM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=BnFL8w+ZEGtcosFKJ0KBAxeXCa/k97n10xMAlB6qsPxBRLzg5VWiAYoQ2pEKkbW9cDoJ6rXjsWGdvyKzK/yJl5eco5xbB7z4uFg/a2ybbBj/jQXluiMTKEufvwLo62JOrQcCcvy+wPiLrkvE0fVmruBCnjAUGd2ENIe/W8AFfME= Received: by 10.142.177.7 with SMTP id z7mr5949389wfe.0.1202374905863; Thu, 07 Feb 2008 01:01:45 -0800 (PST) Received: by 10.142.155.12 with HTTP; Thu, 7 Feb 2008 01:01:45 -0800 (PST) Message-ID: <3a50bd300802070101t7b73f8aalb2e5c65839de6f3e@mail.gmail.com> Date: Thu, 7 Feb 2008 09:01:45 +0000 From: "Sam Crawley" To: users@httpd.apache.org In-Reply-To: <813716b60802061629p5bf5de91xe5230f7ab2276db7@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8276_4503847.1202374905872" References: <3a50bd300802060803t5ee9502j839b5dd87315019b@mail.gmail.com> <813716b60802061629p5bf5de91xe5230f7ab2276db7@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Clustered Reverse proxy ------=_Part_8276_4503847.1202374905872 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks for the response. That's not really going to be an issue in my case, since this cache is sitting at the back end of the application stack, and actually consists of small components that are later assembled into a complete page. The outside world never gets to access the cache directly. I could write an application to do all this of course, but it seems like most of the functionality is already there in a reverse proxy. Sam. On 07/02/2008, Vincent Bray wrote: > > On 06/02/2008, Sam Crawley wrote: > > I'm looking to setup a reverse proxy with Apache 2.2 and mod_cache / > > mod_proxy. I need to be able to do the following things: > > > > 1. Force an item in the cache to expire now (i.e. the next time someone > > accesses it, it will get it from the origin) > > You're missing the fundamental point of http caching: that resources > can be cached by any agent on the wider web based on the constraints > (usually time based) of the original response. Any subsequent requests > can't affect that, for those proxies. I would guess that you'd be > better off getting your application to cache its responses to file. > > -- > noodl > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > > ------=_Part_8276_4503847.1202374905872 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Thanks for the response.

That's not really going to be an issue in my case, since this cache is sitting at the back end of the application stack, and actually consists of small components that are later assembled into a complete page. The outside world never gets to access the cache directly. I could write an application to do all this of course, but it seems like most of the functionality is already there in a reverse proxy.

Sam.

On 07/02/2008, Vincent Bray <noodlet@gmail.com> wrote:
On 06/02/2008, Sam Crawley <mutant.nz@gmail.com> wrote:
> I'm looking to setup a reverse proxy with Apache 2.2 and mod_cache /
> mod_proxy. I need to be able to do the following things:
>
> 1. Force an item in the cache to expire now (i.e. the next time someone
> accesses it, it will get it from the origin)

You're missing the fundamental point of http caching: that resources
can be cached by any agent on the wider web based on the constraints
(usually time based) of the original response. Any subsequent requests
can't affect that, for those proxies. I would guess that you'd be
better off getting your application to cache its responses to file.

--
noodl

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org




------=_Part_8276_4503847.1202374905872--