You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Marc Slemko <ma...@znep.com> on 1997/10/20 01:48:58 UTC
mod_autoindex and caching
Comments?
Getting hit by mirrors 8x for each directory index every x hours isn't
nice.
---------- Forwarded message ----------
Date: 19 Oct 1997 23:40:00 -0000
From: Marc Slemko <ma...@znep.com>
To: apache-bugdb@apache.org
Cc: apache-bugdb@apache.org
Subject: Re: general/1261: Request/patch for SuppressColumnSorting in mod_autoindex
The following reply was made to PR mod_dir/1261; it has been noted by GNATS.
From: Marc Slemko <ma...@znep.com>
To: coar@hyperreal.org
Cc: Apache bugs database <ap...@apache.org>
Subject: Re: general/1261: Request/patch for SuppressColumnSorting in mod_autoindex
Date: Sun, 19 Oct 1997 17:42:23 -0600 (MDT)
On 19 Oct 1997 coar@hyperreal.org wrote:
> Synopsis: Request/patch for SuppressColumnSorting in mod_autoindex
>
> Comment-Added-By: coar
> Comment-Added-When: Sun Oct 19 15:15:03 PDT 1997
> Comment-Added:
> Out of curiousity, why would you want to do this?
Aside from the submitter's reason...
Features are good to disable.
You may not like robots fetching each index 8(!) times just so the user
has the option of sorting it. This is a problem especially since indexes
aren't cachable. Hmm. This is a problem. Check out the log for
www.apache.org and you will see what I mean. Perhaps a last-modified
should be set as the modification time of "." in mod_autoindex?
Re: mod_autoindex and caching
Posted by Dean Gaudet <dg...@arctic.org>.
Oh foo. Well, if any of the options which deal with <Title> are enabled
then this is a bogus mtime, and a full scan like the OS/2 suggestion needs
to be done anyhow.
Dean
On Mon, 20 Oct 1997, Dean Gaudet wrote:
> +1 on using mtime of .
>
> Dean
>
> On Sun, 19 Oct 1997, Marc Slemko wrote:
>
> > Comments?
> >
> > Getting hit by mirrors 8x for each directory index every x hours isn't
> > nice.
> >
> > ---------- Forwarded message ----------
> > Date: 19 Oct 1997 23:40:00 -0000
> > From: Marc Slemko <ma...@znep.com>
> > To: apache-bugdb@apache.org
> > Cc: apache-bugdb@apache.org
> > Subject: Re: general/1261: Request/patch for SuppressColumnSorting in mod_autoindex
> >
> > The following reply was made to PR mod_dir/1261; it has been noted by GNATS.
> >
> > From: Marc Slemko <ma...@znep.com>
> > To: coar@hyperreal.org
> > Cc: Apache bugs database <ap...@apache.org>
> > Subject: Re: general/1261: Request/patch for SuppressColumnSorting in mod_autoindex
> > Date: Sun, 19 Oct 1997 17:42:23 -0600 (MDT)
> >
> > On 19 Oct 1997 coar@hyperreal.org wrote:
> >
> > > Synopsis: Request/patch for SuppressColumnSorting in mod_autoindex
> > >
> > > Comment-Added-By: coar
> > > Comment-Added-When: Sun Oct 19 15:15:03 PDT 1997
> > > Comment-Added:
> > > Out of curiousity, why would you want to do this?
> >
> > Aside from the submitter's reason...
> >
> > Features are good to disable.
> >
> > You may not like robots fetching each index 8(!) times just so the user
> > has the option of sorting it. This is a problem especially since indexes
> > aren't cachable. Hmm. This is a problem. Check out the log for
> > www.apache.org and you will see what I mean. Perhaps a last-modified
> > should be set as the modification time of "." in mod_autoindex?
> >
> >
> >
>
>
Re: mod_autoindex and caching
Posted by Dean Gaudet <dg...@arctic.org>.
+1 on using mtime of .
Dean
On Sun, 19 Oct 1997, Marc Slemko wrote:
> Comments?
>
> Getting hit by mirrors 8x for each directory index every x hours isn't
> nice.
>
> ---------- Forwarded message ----------
> Date: 19 Oct 1997 23:40:00 -0000
> From: Marc Slemko <ma...@znep.com>
> To: apache-bugdb@apache.org
> Cc: apache-bugdb@apache.org
> Subject: Re: general/1261: Request/patch for SuppressColumnSorting in mod_autoindex
>
> The following reply was made to PR mod_dir/1261; it has been noted by GNATS.
>
> From: Marc Slemko <ma...@znep.com>
> To: coar@hyperreal.org
> Cc: Apache bugs database <ap...@apache.org>
> Subject: Re: general/1261: Request/patch for SuppressColumnSorting in mod_autoindex
> Date: Sun, 19 Oct 1997 17:42:23 -0600 (MDT)
>
> On 19 Oct 1997 coar@hyperreal.org wrote:
>
> > Synopsis: Request/patch for SuppressColumnSorting in mod_autoindex
> >
> > Comment-Added-By: coar
> > Comment-Added-When: Sun Oct 19 15:15:03 PDT 1997
> > Comment-Added:
> > Out of curiousity, why would you want to do this?
>
> Aside from the submitter's reason...
>
> Features are good to disable.
>
> You may not like robots fetching each index 8(!) times just so the user
> has the option of sorting it. This is a problem especially since indexes
> aren't cachable. Hmm. This is a problem. Check out the log for
> www.apache.org and you will see what I mean. Perhaps a last-modified
> should be set as the modification time of "." in mod_autoindex?
>
>
>
Re: mod_autoindex and caching
Posted by Marc Slemko <ma...@worldgate.com>.
On Mon, 20 Oct 1997, Brian Behlendorf wrote:
> At 05:48 PM 10/19/97 -0600, Marc Slemko wrote:
> >Getting hit by mirrors 8x for each directory index every x hours isn't
> >nice.
>
> Adding support for SuppressColumnSorting sounds fine to me.
>
> Are directory indexes uncacheable? Seems to me one could do a stat() on
> the directory itself and if it hadn't changed, then return a 304...
I was thinking the same thing; in fact, I mentioned the same thing a few
lines down in the message you replied to.
I'm thinking that adding last-modified code would be useful. I think it
should be valid on all Unix systems.
No comment on that Windows stuff or OS/2...
Re: mod_autoindex and caching
Posted by Brian Behlendorf <br...@organic.com>.
At 05:48 PM 10/19/97 -0600, Marc Slemko wrote:
>Getting hit by mirrors 8x for each directory index every x hours isn't
>nice.
Adding support for SuppressColumnSorting sounds fine to me.
Are directory indexes uncacheable? Seems to me one could do a stat() on
the directory itself and if it hadn't changed, then return a 304...
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
"it's a big world, with lots of records to play." - sig brian@organic.com