Thanks for your response and guidance. I think I'm going to iterate over my conatainer's *_view and segment it into different page templates (so I can assess bottleneck sections) and also strip out any unecessary logic into separate (cachable) python scripts.
At least I know I'm not missing any obvious on my cachefu set up. Thanks again. Ricardo Newbery-2 wrote: > > > On Jan 30, 2009, at 10:31 AM, Finlay Boo wrote: > >> >> Looking into this, I'm thinking that my issue is that, as my site in >> an >> intranet, whereby all users are authenticated then caching can be a >> problem >> with even subtle content variations such as the user's name >> displaying in >> the personal bar. The vast majority of users see the site version of >> the >> site but there are occasional pages which are limited to a small >> number of >> users. >> >> Therefore, as I would guess that an intranet with Active Directory >> authentication is a reasonably, popular configuration can any one >> advise how >> they've configured their container caching? I currently have this >> set with >> 'cache-with-etag' for authenticated users: >> >> Cache Templates in Memory: Not checked >> Last Modified Header; Yes >> Etag Header: Yes >> Enable 304s: Yes >> Vary Header: Yes >> max-age : 0 >> s-maxage: 0 >> Cache control Header: must revalidate: yes >> Cache control Header: public: yes >> (All other Cache control Headers are unset) >> >> I'm using CacheFu 1.2 with Plone 3.1.7 with Apache (but no squid or >> varnish >> as yet) >> >> Anyone who has been through hours of tweaks and enjoyed successful >> results >> care to share? > > > There is very little you can do, cache-wise, for personalized views > except for what you have done here. Although I would delete the Last- > Modified Header as you can specify this info in an Etag and there are > cases in IE where specifying both can cause incorrect behavior. Also > unset the 'public' cache control token as this is only needed to > communicate that it's okay to store the content into a shared cache > (set the 'private' token instead). You should also make sure the Etag > has all the components it needs to ensure the most current page can be > fully specified. > > In other words, what you want is the original settings for the 'cache- > with-etag' shipped with the default policy. :-) > > One potential way to open up all sorts of caching possibilities for an > authenticated view is to tweak the site templates to de-personalize > the views. Not easy but it can be done as long as the only > personalized bits are those usernames, logout links and the like. > > Ric > > > > _______________________________________________ > Setup mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/setup > > -- View this message in context: http://n2.nabble.com/CacheFu-Configuration-tp2158607p2249346.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
