httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: mod_cache caching the 301 Moved Permanently
Date Fri, 22 Apr 2005 20:49:24 GMT

Olaf van der Spek wrote:
> On 4/22/05, Justin Erenkrantz <> wrote:


>>I don't get it.  What's your problem?  -- justin
> The 'here' link is to
> while he wants it do be to

His problem is a different one. If you type
(without the slash) you have the following headers (first my request / second server reply):

GET /where-to-buy HTTP/1.1
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050319
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plai
Accept-Language: de,en;q=0.8,de-de;q=0.5,en-gb;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive

HTTP/1.x 200 OK
Date: Fri, 22 Apr 2005 20:39:58 GMT
Server: Apache
Content-Type: text/html; charset=iso-8859-1
Cache-Control: max-age=432000
Expires: Tue, 26 Apr 2005 04:58:38 GMT
Content-Length: 256
Age: 142880
Keep-Alive: timeout=3, max=20
Connection: Keep-Alive

The problem seems to be, that the proxied backend server that is cached via mod_disk_cache
delivers HTTP status 301 and the Location, but
once cached
mod_disk_cache delivers HTTP status 200 instead of 301 (but correctly redelivering the Location
I have not proved this for myself so far, but this seems the problem to me.

I think the difference between the here link and the Location header can be explained by the
directive which rewrites the Location header, but not the HTML code in the error page.



View raw message