in reply to Re: Apache::CacheContent and unforeseen side effects
in thread Apache::CacheContent and unforeseen side effects

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.

  • Comment on Re^2: Apache::CacheContent and unforeseen side effects

Replies are listed 'Best First'.
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]

In Section Seekers of Perl Wisdom