Hi Jan,
thanks for your answer but I'm still struggling with the browser cache policy.
Here is my configuration:
/modules/cache/config/configurations/default/browserCachePolicy/policies:
[code]
- farFuture
- voters
- dotCacheExtension
class = info.magnolia.voting.voters.URIRegexVoter
pattern = .*\.cache\.[^\.]*
class = info.magnolia.module.cache.browsercachepolicy.FixedDuration
expirationMinutes = 525600
- resources
- voters
- dotResources
class = info.magnolia.voting.voters.URIStartsWithVoter
pattern = /.resources/String
- contentType
- allowed
css = text/css
javascript = application/x-javascript
class = info.magnolia.voting.voters.ResponseContentTypeVoter
op = OR
class = info.magnolia.module.cache.browsercachepolicy.FixedDuration
expirationMinutes = 7200
- stkThemeImages
- voters
- theme-images
class = info.magnolia.voting.voters.URIStartsWithVoter
pattern = /resources/templating-kit/themes/
op = OR
class = info.magnolia.module.cache.browsercachepolicy.FixedDuration
expirationMinutes = 7200
- default
class = info.magnolia.module.cache.browsercachepolicy.FixedDuration
expirationMinutes = 10
- webPages
- voters
- sites
class = info.magnolia.voting.voters.URIStartsWithVoter
pattern = /
class = info.magnolia.module.cache.browsercachepolicy.FixedDuration
expirationMinutes = 33
[/code]
I hope my visulation is self describing :)
Well my server response looks like that
[code]
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Vary: Accept-Encoding
Content-Encoding: gzip
Last-Modified: Fri, 15 Mar 2013 13:08:06 GMT
Pragma:
Content-Type: text/html;charset=UTF-8
Content-Language: en
Transfer-Encoding: chunked
Date: Fri, 15 Mar 2013 13:08:10 GMT
[/code]
So I am missing every cache configuration :(
That made me kind of suspicious and I looked for more configurations (in debug
mode I saw some set cache headers, but I was not able to follow the response
object until it has been overwritten). I found the executors which I don't
understand very well. The documentation doesn't make me much cleverer. It says
there can be bypassed a cache. So in case of server side caching I understand
this. But client site caching (html header cache control) I don't understand.
Under /modules/cache/config/configurations/default/executors there are content
nodes named bypass, store and useCache each with the following content node
inside
[code]
- setExpirationHeader
class = info.magnolia.module.cache.executor.SetExpirationHeaders
[/code]
Hm. So I expect these executors are responsible for setting the cache. They are
set in every case so they should do their work. The point where I really lose
my mind is when the SetExpirationHeaders loads the browser cache policy. When I
am debugging, the first few times the class is called some cache times are set
correctly. Later on, after being called many many times (I suspect for each
component?), the header cache is being disabled. But I have no clue who did
this :-) So there must be a misconfiguration from my side, doesn't it? Well on
the demopublic side the cache expires at Thu Jan 01 1970 01:00:00 GMT+0100 too
every time.
Thanks for your time
Wolfgang :-)
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=8526d3dc-e1f2-437e-bb43-183fc50b99ba
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
