hey, it could have been that somebody else just solved this problem... That was my initial hope ;)
Ok, the expiration header is always set to 30 Minutes...and that is the default value of the info.magnolia.module.cache.browsercachepolicy.FixedDuration class. The configured value is not used - i guess. regards rainer gregoryjoseph wrote: > > > On Dec 22, 2008, at 5:53 PM, rainer wrote: >> Hi list, >> >> i know there was a post for that topic short time ago. but it didnt >> really >> help. >> >> I need to deactivate the Client-side Caching - and it doesnt work... >> in >> magnolia i tried to set: >> >> 1. expirationMinutes = 0 >> 2. i changed the "browserCachePolicy" class to >> "info.magnolia.module.cache.browsercachepolicy.Never" >> >> nothing helped. >> >> The Browsers are still Caching and also the default: 30 Minutes >> doesnt seem >> to be interpreted correctly. >> >> Do you have any hints? > > Yes: plug your debugger in, and/or use tools like "live http headers" > in firefox to see what headers are sent with which values, and what > causes the issue. > > Without any info, other than "it doesn't work", there's hardly > anything anyone could do for you, except maybe using a crystal ball. > > -g > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > -- View this message in context: http://www.nabble.com/Expiration-Header-%2B-BrowserCachePolicy-tp21131035p21134720.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
