httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Stoneman <>
Subject Re: HTTP headers on 'trailing slash' redirects?
Date Mon, 12 Aug 2002 10:47:22 GMT
Monday, August 12, 2002, 9:09:01 AM, you wrote:

> Phil Stoneman says:
>> Now, my problem is this: Apache(1.3.26) is sending 301
>> (HTTP_MOVED_PERMANENTLY) when it does the 'trailing slash' redirects
>> to contruct a valid URI for a directory. This is technically not
>> against the RFC from what I can see. It is a bit annoying, though,
>> since when tinkering with UseCanonicalName in the config file, the
>> browser cached the redirect and made me think apache wasn't getting
>> its own hostname correctly.
>> I've tested IIS 5.0, and this does seem to send 302
>> (HTTP_MOVED_TEMPORARILY), which is what I'd imagine should be done.
>> Also, I've found a reference on google groups to apache 1.2b8 where
>> this behaviour was changed as I'm looking for:
>> (The bit in question was written by Markus Gyger, and is about halfway
>> down)

> Seems to me that a URL pointing to a directory always has to end with a 
> slash, and therefor it is permanent. Why would it be temporary?

Hmm... I'm not entirely sure, to be honest. I wouldn't really
consider myself experienced in any way with the inner workings of web
It does strike me that the object could concievably change between
being a directory and being a file, for example, meaning that a cached
redirect (Which is what seems to happen with a permanent redirect) is
an annoyance.

Also, it appears that IIS (at least 5.0, which I've tested for this)
and Apache 1.2b8 (from that changelog I found) do respond with a 302
(temporary redirect). I'm wondering why the current Apache's behaviour
is different, that's all.

Also, is there any way to persuade apache to do this right with



 Phil Stoneman                  

View raw message