Return-Path: 
 <dev-return-72891-apmail-httpd-dev-archive=httpd.apache.org@httpd.apache.org>
X-Original-To: apmail-httpd-dev-archive@www.apache.org
Delivered-To: apmail-httpd-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 633F179FA
	for <apmail-httpd-dev-archive@www.apache.org>;
 Thu,  6 Oct 2011 17:03:39 +0000 (UTC)
Received: (qmail 20838 invoked by uid 500); 6 Oct 2011 17:03:38 -0000
Delivered-To: apmail-httpd-dev-archive@httpd.apache.org
Received: (qmail 20788 invoked by uid 500); 6 Oct 2011 17:03:38 -0000
Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
list-help: <mailto:dev-help@httpd.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@httpd.apache.org>
List-Post: <mailto:dev@httpd.apache.org>
List-Id: <dev.httpd.apache.org>
Delivered-To: mailing list dev@httpd.apache.org
Received: (qmail 20780 invoked by uid 99); 6 Oct 2011 17:03:38 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2011 17:03:38 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of amila.uoc@gmail.com designates
 74.125.82.173 as permitted sender)
Received: from [74.125.82.173] (HELO mail-wy0-f173.google.com) (74.125.82.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2011 17:03:30 +0000
Received: by wyh22 with SMTP id 22so4482108wyh.18
        for <dev@httpd.apache.org>; Thu, 06 Oct 2011 10:03:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=U8LYu9FATFSpQOCIhlfySh4u99uXS7xZwGIwFvZIhmM=;
        b=OB9altr80Ug3oYxTSb2zMvpbERiSyIFL8IdBUhcUlnk0Pts0l9dzX8thj4wtgte6dc
         VYVf3fvEmROtAEcV9Wdw+P8GCfKklFAgrtbb9gHoaOXnNANt2tDNWrPmhMWpG56sDl3w
         Rz0kuqt2IVUWeqrGIcwM/Cs7zMmuVcf8fM1gE=
MIME-Version: 1.0
Received: by 10.216.14.223 with SMTP id d73mr551806wed.55.1317920590730; Thu,
 06 Oct 2011 10:03:10 -0700 (PDT)
Received: by 10.216.221.159 with HTTP; Thu, 6 Oct 2011 10:03:10 -0700 (PDT)
Date: Thu, 6 Oct 2011 22:33:10 +0530
Message-ID: 
 <CAKa-J=GFWpWPNZ34iQ+nZqsdBvy_fRgPSYp4sUBDe_P1kF9v1g@mail.gmail.com>
Subject: Caching - Generating E-Tags
From: Amila Liyanaarachchi <amila.uoc@gmail.com>
To: dev@httpd.apache.org
Content-Type: multipart/alternative; boundary=001485f85940a7160b04aea44c12
X-Virus-Checked: Checked by ClamAV on apache.org

--001485f85940a7160b04aea44c12
Content-Type: text/plain; charset=ISO-8859-1

Hi Dev,

I'm working on a caching protocol similar to HTTP on a different research. I
have the following question regarding the e-tags.
When does exactly apache computes the e-tag for a certain resource?
Does it compute that when there is a request for that particular resource or
is it computed by the server whenever a resource get modified in the
server?

Thanks,
Amila

--001485f85940a7160b04aea44c12
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Dev,<div><br></div><div>I&#39;m working on a caching protocol similar to=
 HTTP on a different research. I have the=A0following question=A0regarding =
the e-tags.</div><div>When does exactly apache computes the e-tag for a cer=
tain resource?</div>
<div>Does it compute that when there is a request for that=A0particular res=
ource or is it computed by the server whenever a resource get modified in t=
he server?=A0<br clear=3D"all"><div><br></div>Thanks,<br>Amila<br>
</div>

--001485f85940a7160b04aea44c12--