Re: Apache::CacheContent and unforeseen side effects

Apache::CacheContent is mostly a proof of concept. I recommend you ditch it and use it a cache reverse proxy instead. In addition to the basic caching features, it will also handle conditional-get (If-Modified-Since) for you. You really should be running a reverse proxy anyway with any mod_perl server that's getting siginificant traffic.

Comment on Re: Apache::CacheContent and unforeseen side effects

Replies are listed 'Best First'.
Re^2: Apache::CacheContent and unforeseen side effects by geektron (Curate) on Dec 27, 2004 at 21:34 UTC
i did ditch Apache::CacheContent -- in favor of a simple Cache::FileCache solution that just caches the needed data fro mthe 3rd party site. took me about an hour, including reading the perldoc on it ... reverse proxy? i don't see how this would solve the problem. our servers are fine ... it's the 3rd party site that has the issues with the hits.	[reply]
Re^3: Apache::CacheContent and unforeseen side effects by perrin (Chancellor) on Dec 28, 2004 at 05:29 UTC
Apache::CacheContent caches the whole generated page. So does a caching reverse proxy. That's why one is a good substitute for the other.	[reply]