On Tue, 19 Dec 1995, Jan Schubert wrote:
> There is a problem with cancelling transfers. If the transfer is cancelled
> by the user, the browser stops immedially, but not the proxy-server.
> Is there a way to tell the proxy, that the transfer should be cancelled ?
> How ?
No, the httpd continues to collect the document so that it will have a
complete document in its cache. Read the SIGPIPE handler.
> 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.
> The second question is, how can I cache alle pictures, which transfered with
> HTTP, but no CGI-files. It seemes, the proxy can either cache all
> HTTP-transfers or nothing else HTML-files.
> At this time, after the daily garbage-collection all pictures will be
> erased, but no HTML-files.
Cern httpd decides on whether to cache by 7 criteria. One of these is
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.
It sounds like your configuration is odd. You really want to have
CacheClean 2 months
CacheUnused http:* 7 days
CacheUnused ftp:* 7 days
CacheUnused gopher:* 7 days
# 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