httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <>
Subject Re: CGI output caching
Date Mon, 26 Jan 1998 22:41:24 GMT
You can't normally do CGI caching in the web server because you don't know
what the output is based on.

Now, if you have a CGI and you know its output is based on the
query string, for example, then you may be able to safely cache that if
you decide that the data it is getting will not change too often, etc.

Normally the better solution is to change the CGI into some other method
(eg. module, mod_perl. mod_fastcgi, etc.) so you remove the CGI overhead
and then cache at some lower layer if you are pulling it from a database,
etc.  The times when you can usefully cache CGI output are very limited
and require extensive manual configuration.

On Mon, 26 Jan 1998, Igor Tatarinov wrote:

> Hi folks,
> Sorry I've already asked this question but didn't get any answer. Is the
> idea absolutely dumb or what?
> What I am thinking of is caching of CGI output. I know that it's tough and
> not always useful (I hear you saying "Don't cache our counter, you moron!).
> But everytime I visit imdb (hi Rob!) I think that it may worth it.  Just
> think of eliminating the need to start a new perl process and execute it.
> Of course, in some situations it might be a bad idea. The main problem is
> probably that the length of the output stream is unknown. 
> Yeah, it may be tougher than I think and isn't it what proxies are for? 
> anyway your comments are welcome
> igor

View raw message