On Tue, 24 May 2005, Matthias Wessendorf wrote:
perhaps I also shoult tell you,
that the dynamic content is protected (via BASIC authentication)
any ideas regarding such an issue
caching of dynamic and *protected* content ?
HTTP specifications normally forbid caching of such content.
For Squid to cache password protected content the content must be marked with "Cache-Control: public" telling the cache that while the request carried authorization credentials the resulting object doesn't really require authentication and can be cached.
In addition the refresh rules needs to indicate the object is fresh for at least 60 seconds. Either by Last-Modified/Expires information in the reply or by refresh_pattern settings in squid.conf. (note: if there is Last-Modified information the limit is 1 second, not 60).
Regards Henrik
