+1.
On the topic of redirects... when I access http://www.microsoft.com/ right
now, I get redirected _FOUR_ times before reaching an actual document.
Sheesh.
On Sat, 1 Feb 1997, Dean Gaudet wrote:
> Submitted by: Markus Gyger <mgyger@itr.ch>
>
> Issue a 301 response instead of a 302 response when returning a directory
> redirect for "/foo" to "/foo/". This allows the redirect to be cached.
>
> Nothing in rfc2068 would lead me to belive this is a bad idea. But one
> problem that might occur is the inability to change "/foo" to a file or
> other resource instead of a directory without caching problems. But this
> is true of a bunch of things...
>
> Navigator seems to only cache the redirect in memory not on disk.
>
> Netscape-Enterprise/2.01, and CERN/3.0A issue 302s just like Apache
> presently does.
Spyglass_Server/2.00fc3 returns a 301. So does
Cheetah_Web_Server/1.01fc5.
(Hehe. I love it. One document says "This page is served using our GLACI
HTTPD server on Netware". Funny, your server thinks it is CERN.)
>
> I'm all for improving cacheability.
>
> Dean
>
> Index: mod_dir.c
> ===================================================================
> RCS file: /export/home/cvs/apache/src/mod_dir.c,v
> retrieving revision 1.20
> diff -c -3 -r1.20 mod_dir.c
> *** mod_dir.c 1997/01/12 20:11:53 1.20
> --- mod_dir.c 1997/02/01 22:33:23
> ***************
> *** 784,790 ****
>
> table_set (r->headers_out, "Location",
> construct_url(r->pool, ifile, r->server));
> ! return REDIRECT;
> }
>
> /* KLUDGE --- make the sub_req lookups happen in the right directory.
> --- 784,790 ----
>
> table_set (r->headers_out, "Location",
> construct_url(r->pool, ifile, r->server));
> ! return MOVED;
> }
>
> /* KLUDGE --- make the sub_req lookups happen in the right directory.
>
|