httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Axel-Stéphane SMORGRAV <>
Subject [users@httpd] RE : [users@httpd] mod_cache: how to determine its running
Date Tue, 23 Nov 2004 07:17:44 GMT
Doesn't it even say something like "cache: no cache" ??

Could you mail the relevant parts of the logs?


-----Message d'origine-----
De : Sean T Allen [] 
Envoyé : lundi 22 novembre 2004 16:53
À :
Objet : Re: [users@httpd] RE :mod_cache: how to determine its running

Well what i see for debug output is the content getting cached... then nothing... only access
log, no debug information and the response header continues to read thttpd ( yet you'd think
it'd see the 
proxy debug output
but I don't ).

I am thoroughly stymied by now.

Axel-Stéphane SMORGRAV wrote:

>The headers are cached along with the document, and they are served by 
>the cache.
>As far as headers are concerned, in your case the back-end server is 
>thttpd; if the document is served from your Apache cache I believe the 
>Server header should read "Apache".
>If you turn on debug, you'll figure out how to determine whether a file 
>is cached, and whether it is server from cache, very easily. The debug 
>output from the cache modules is very explicit.
>-----Message d'origine-----
>De : Sean T Allen []
>Envoyé : lundi 22 novembre 2004 16:07
>À :
>Objet : Re: [users@httpd] RE :mod_cache: how to determine its running
>My question then becomes... what should i see in the logfile that would
>indicate that a file is being served from
>the cache. And why if a file was cached, would i see headers from the 
>server it was originally proxied from...
>Axel-Stéphane SMORGRAV wrote:
>>To answer the question in the subject line, set the LogLevel to debug
>>and look in the error log. That should enable you to determine whether 
>>a particular document is cached, and if it is not, determine the reason 
>>for that.
>>>>From the look of the response headers the document should be cached.
>>>You should also have a look at the request headers and make sure that
>>>there is no "Cache-Control: no-cache".
>>-----Message d'origine-----
>>De : Sean T Allen []
>>Envoyé : dimanche 21 novembre 2004 04:48
>>À : apachehelp
>>Objet : [users@httpd] mod_cache: how to determine its running
>>Server version: Apache/2.0.52
>>Compiled in modules:
>> core.c
>> mod_access.c
>> mod_auth.c
>> mod_cache.c
>> mod_disk_cache.c
>> mod_mem_cache.c
>> mod_log_config.c
>> mod_env.c
>> mod_setenvif.c
>> mod_proxy.c
>> proxy_connect.c
>> proxy_ftp.c
>> proxy_http.c
>> mod_ssl.c
>> prefork.c
>> http_core.c
>> mod_mime.c
>> mod_status.c
>> mod_autoindex.c
>> mod_dir.c
>> mod_imap.c
>> mod_actions.c
>> mod_alias.c
>> mod_rewrite.c
>> mod_so.c
>>And lastly issue...
>>I am reverse proxying to an httpd server instance running on
>> Have a mem_cache setup that doesnt seem to be 
>>Here are some snippets:
>>CacheEnable mem /
>>CacheRoot /cache/toppik
>>CacheSize 5000000
>>CacheGcInterval 1
>>CacheLastModifiedFactor 0.1
>>CacheDefaultExpire 3600
>>CacheMaxExpire 43200
>>CacheForceCompletion 60
>>#CacheIgnoreCacheControl On
>>CacheIgnoreNoLastMod On
>>MCacheMaxObjectCount 10000
>>MCacheMaxObjectSize 12800000
>>MCacheMinObjectSize 0
>>MCacheRemovalAlgorithm LRU
>>MCacheSize 100000
>>There are some disk cache related things in there as I was playing 
>>around with it during test.
>>and the mod-rewrite stuff that proceeds the cache entries in the 
>>RewriteEngine On
>># send all requests to www
>>RewriteCond %{HTTP_HOST}   !^www\.toppik\.info [NC]
>>RewriteCond %{HTTP_HOST}   !^$
>>RewriteCond %{SERVER_PORT} ^443$
>>RewriteRule ^/(.*)$1 [L,R]
>>RewriteCond %{HTTP_HOST}   !^www\.toppik\.info [NC]
>>RewriteCond %{HTTP_HOST}   !^$
>>RewriteRule ^/(.*)$1 [L,R]
>># tracking rewrite
>>RewriteCond %{QUERY_STRING} ^(.*)&keyword=([^&]+)&?(.*) RewriteRule
>>^/s-([^/]+)/(.*) /s-$1&kw=%2/$2?%1&%3 RewriteCond %{QUERY_STRING} ^keyword=([^&]+)&?(.*)
RewriteRule ^/s-([^/]+)/(.*) /s-$1&kw=%1/$2?%2 RewriteCond %{QUERY_STRING} ^(.*)&olid=([^&]+)&?(.*)
RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%2/$2?%1&%3 RewriteCond %{QUERY_STRING} ^olid=([^&]+)&?(.*)
RewriteRule ^/s-([^/]+)/(.*) /s-$1&olid=%1/$2?%2 # dynamic rewrite RewriteRule ^/(s-[^/]*)(/(.*?))*(/mp)+/(.*)$$1/$5 [P] RewriteRule ^(/(.*?))*(/mp)+/(.*)$$4
[P] # admin rewrite RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/admin/(.*)$$1
[R,L] RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/(s-[^/]*)/admin/(.*)$$1/admin/$2
>>RewriteRule ^/(s-[^/]*)/admin/(.*)$$1/admin/$2 [P] RewriteRule
^/admin/(.*)$$1 [P] # lid mapping rewrite RewriteRule ^/s-[^/]*/(.*)
/$1 # hit tracking rewrite RewriteRule /ht.gif$ /images/ht.gif [QSA] # awstats RewriteRule
/(awstat.*)$1 [P] # static file rewrite #RewriteRule /(server.*) /$1
[L] RewriteRule (.*)$$1 [P]
>>Standard response header example:
>>Date: Sun, 21 Nov 2004 04:34:49 GMT
>>Server: thttpd/2.25b 29dec2003
>>Content-Type: text/html; charset=iso-8859-1
>>Last-Modified: Fri, 19 Nov 2004 21:26:26 GMT
>>Accept-Ranges: bytes
>>Content-Length: 35484
>>Cache-Control: max-age=43200
>>Expires: Sun, 21 Nov 2004 16:34:49 GMT
>>Some where o where do I have this misconfigured?
>>Order that module compiled in?
>>Something esoteric in the setup?
>>Freaky rewrite rule getting in the way?
>>Your help greatly appreciated...

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message