Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of flo.sch@gmx.net designates
 213.165.64.20 as permitted sender)
From: "Florian S." <flo.sch@gmx.net>
To: users@httpd.apache.org
In-Reply-To: <n2m4df3a1331004130734n1658bb81kfb57a28b94497c9b@mail.gmail.com>
References: <n2m4df3a1331004130734n1658bb81kfb57a28b94497c9b@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 13 Apr 2010 22:50:17 +0200
Message-ID: <1271191817.3245.7.camel@florian-desktop>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [users@httpd] Custom ETags

Am Dienstag, den 13.04.2010, 10:34 -0400 schrieb Brian Mearns:
> I'd like to use stronger and correlated ETag, namely the hash of the
> content being served. Obviously it's a drag to do this in-line, so I'm
> planning an automated task to generate the ETag values and store them
> on the server. Is there any way I can get httpd to grab these stored
> values for use in the Etag header? I'm flexible on how I store them:
> in a database, in one large file, each in its own file named according
> to the resource, etc.
> 
> Any ideas?
> 
> Thanks,
> -Brian
> 

Hi,

Here a short presentation of how I would face this problem:
I found a nice & powerful way of including external scripts depending on
URL/I: RewriteMap. I think its performance is sufficient, since the
process gets spawned only once and the stdio-stuff happens only.
Text-Databases are supported, too. The output (the ETag?) could be
stored in a Envar with a corresponding RewriteRule (E-flag). Then you
can do a few checks and/or use 'Header set ETag new_tag env=new_tag' or
something similiar.

Not tested at all & sounds strange, but may be a starting point.

Regards:
	Florian


---------------------------------------------------------------------
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