> > Are there some other proxy-server without this problem ? >
> Why is it a problem? Harvest cached handles it in approx the same manner
> as cern httpd.
No, there is a quick abort option for the harvest cached. I always choose
that - otherwise you'll get (almost) eternal stream of pictures flowing
from some advanced sites which employ multipart/mixed animations
> the presence of Content-length: in the header which gives the correct
> content length. Most cgi scripts do not take the trouble to return a
> Content-length: header, and are thus not cached. Sometimes it is worth
> writing cacheable script output, sometimes it is not.
Basically, you shouldn't cache cgi-bin's. Very few people always return
the same stuff from cgi - ( obvious )
You shouldn't also cache shtml ( server side includes ) docs.
Same reason - why put burden on the server if plain doc will suffice.
> # Specify default expiry times for ftp and gopher;
> # NEVER specify it for HTTP, otherwise documents generated by
> # scripts get cached which is usually a bad thing.
> CacheDefaultExpiry ftp:* 7 days
> CacheDefaultExpiry gopher:* 2 months
> CacheLastModifiedFactor 0.5
In case of harvest cache, you can ( almost) safely cache html's as well.
Anyway, you can always press 'Reload' in Netscape/Mosaic, and harvest
cache will _correctly_ reload this page from the source
Slava Kritov * http://www.freenet.kiev.ua/scorp
Senior Internetwork Specialist * http://elfstone.un.kiev.ua/
UN Internet Project for Ukraine * http://www.un.kiev.ua/
*** Finger scorp @
ua for public PGP key ***