Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 19259 invoked by uid 6000); 29 Dec 1998 18:08:51 -0000 Received: (qmail 19217 invoked from network); 29 Dec 1998 18:08:48 -0000 Received: from twinlark.arctic.org (204.62.130.91) by taz.hyperreal.org with SMTP; 29 Dec 1998 18:08:48 -0000 Received: (qmail 15352 invoked by uid 500); 29 Dec 1998 18:25:53 -0000 Date: Tue, 29 Dec 1998 10:25:53 -0800 (PST) From: Dean Gaudet To: new-httpd@apache.org Subject: Re: cvs commit: apache-1.3/src/support httpd.exp In-Reply-To: <19981229094620.23597.qmail@hyperreal.org> Message-ID: X-Comment: Visit http://www.arctic.org/~dgaudet/legal for information regarding copyright and disclaimer. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On 29 Dec 1998 fielding@hyperreal.org wrote: > +/* Create a variant list validator in r using info from vlistr. */ > + > +static void set_vlist_validator(request_rec *r, request_rec *vlistr) > +{ > + /* Calculating the variant list validator is similar to > + * calculating an etag for the source of the variant list > + * information, so we use ap_make_etag(). Note that this > + * validator can be 'weak' in extreme case. > + */ > + > + ap_update_mtime (vlistr, vlistr->finfo.st_mtime); > + r->vlist_validator = ap_make_etag(vlistr, 0); > + > + /* ap_set_etag will later take r->vlist_validator into account > + * when creating the etag header > + */ > +} mod_negotiation isn't the only module that can do negotiations... what happens if a sub request also has a vlist_validator because it was negotiated? (Maybe I don't understand vlist_validator... maybe you could put a couple more notes into httpd.h ;) Dean