On Tue, 19 Apr 2005, Oliver Joa wrote:
Thank you, i will try, but maybe i found the problem already: Is it true that Url which are protected by login/password (Authentication-Type: Basic) are not cachable?
Correct, as these are private to the user and the server needs to be contacted to verify the authentication.
If it is true, how can it be cached?
You can have the server send "Cache-Control: public" to allow shared caches to cache the object. This tells caches that even thou the request contained authentication credentials the resulting reply is public and is not restricted by authentication.
RFC 2616 14.8 Authorization, paragraph 3. Only the third alternative is implemented by Squid.
Regards Henrik