Re: [squid-users] No objects in cache when using http authentication

On 01.03.2012 20:27, milutin_at_s3rsync.com wrote:
> Hello,
>
> I'm using squid as a reverse proxy to accelerate access to some
> remote site.
>
> This site have HTTP authentication on top of application
> authentication to avoid spiders etc. I my case there is one general
> username/password to the site.
>
>
> I have noticed that Squid don't save objects in cache when the site
> use http authentication.
>
>
> Is it suppose to be like that?

Yes authentication requirement implies private data. private data is
not to be cached for sharing around.

> If yes, are there is a way workaround it?

Your server should send the header "Cache-Control:public" on any
objects which are authenticated but able to be shared around to any
visitor.

That said, your Squid is HTTP/1.0 software and does not obeying that
HTTP/1.1 directive. The more recent HTTP/1.1 squid have not yet reached
the point of implementing it. Patches are very welcome.

>
> Other question, dose squid in reverse proxy configuration of ssl site
> will save objects in cache?

Yes. The SSL ends at the proxy and the decrypted content can be cached
and/or served out of cache.

Amos
Received on Thu Mar 01 2012 - 09:14:43 MST