Henri Bergius schrieb:
Hi!
On Nov 27, 2007 3:58 PM, Andreas Flack <[EMAIL PROTECTED]> wrote:
Turning the new content caching mechanism on and off doesn't have any
influence on this. Before the update, the site ran for almost a year on
2.6 without having this problem. I didn't make any changes to the
website configuration, so I wanted to ask if there where any changes to
the way cache (or expires, or whatever) headers are set or if anyone has
any idea what else might cause this problem.
The content cache and caching headers sent by MidCOM are two different
things (though the 'content' module deals with both).
Try adding this to your style:
$_MIDCOM->cache->content->enable_live_mode();
This should kill all browser/proxy caches.
Yeah, it works, although I still wonder why this is necessary in 2.8 and
not in 2.6 (unless of course if this was the default for all requests in
2.6). Also, won't this negatively affect page load times if the browser
isn't allowed to cache anything any more?
(BTW, we could consider doing that for Asgard)
Well, ATM Asgard is completely unusable on IE6 anyways, so if this is
really the only browser affected by this issue, maybe it would be easier
just to do a browser detection in the _can_handle phase and die with the
message "install a real browser first" or something like that :-)
Bye,
Andreas
Andreas
/Henri
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
