On 06.06 14:19, Peter Zechmeister wrote: > - Squid must not cache pages, where Authorization Header is set, but it > does in the moment and so pages which have the same url but behave > different when entered anonymous or autorized are mixed up. > Can anybody tell me how to fix this? see section 14.8 of RFC2616, that explains when squid is allowed to cache authorized pages. Look at Cache-Control: headers in request and response. > - One step further would be, to cache personalized pages too, but with > a personalized cache. We have an intranet with a lot of roles and > restricted areas. If somebody is logged in, the username is shown on > each page and menues have to be rendered according to the permissions of > that person. The on-demand generation of those personalized pages is > much more expensive than to store thousands of pre-generated pages in > the cache. The same as above. Cache-Control is your friend, you need to set it up properly. -- Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. I wonder how much deeper the ocean would be without sponges.
