httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dick Snippe <>
Subject [users@httpd] mod_cache broken in 2.2.0 ?
Date Fri, 09 Dec 2005 11:01:27 GMT

we use apache-2.0.x as a reverse caching proxy, using mod_cache,
mod_mem_cache, mod_proxy and mod_proxy_http.
Basically by saying
	CacheEnable mem /
	ProxyPass	/	http://tomcatserver:8888/
(okay, there is some more configuration involved, but this is the basic
idea. We've been running apache-2.0 in this setup for almost 3 years now,
so we're quite familiar with mod_cache in 2.0).

When trying a similar setup in apache-2.2.0 this fails.
Entries appear to be cached, but the hostname that is used when stuff is put
in the cache is "_default_".
On the next hit, apache checks to see if it is cached already, but here it
doesn't use "_default_", but the supplied http Host: name.
So, it can't find the entry in the cache.

I'm inclined to say that this behaviour is caused by apparently faulty logic
in modules/cache/cache_storage.c, around line 357:
	/* We are a proxied request, with no hostname. Unlikely
	 * to get very far - but just in case */
	hostname = "_default_";

Does anybody else have this problem?
Could it have something to do with UseCaninicalName On/Off
and/or name based virtual hosting?

Dick Snippe - een Coordinator Publieke Omroep Internet Services
Gebouw 12.401 (peperbus) Sumatralaan 45 Hilversum  \ fight war
tel +31 35 6774252, email []()     \ not wars

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