My url structure is domain.com/cat_name/article_name.html

Cached folder stored the same structure as domain one
-cached
–cat_name
—–article_name.html.html
–cat_name_1
—–article_name_1.html.html

I tried to mess up with htaccess rule but failed. Could you point me anything to make it work ?

Cheers
holo

http://www.somedomain.com/action/controller/param/param/

In this case the trailing slash causes the rewrite condition that checks for the existence of a cached file to fail. I fixed this by adding the following before the rule that rewrites to the cached file.

RewriteRule ^(.*)/$ $1 [NC,L]

Some may suggest that this should be a redirect instead, but I decided to use the NC because I like my urls to contain a trailing slash.

Again, thank you Brandon for this post, and thank you to Pádraic for an awesome addition to ZF.

Its been a while since I’ve looked into page caching, and I had moved on to using frontend content servers (Nginx and mpm-worker with mod_cache) for caching.

Maybe I’ll finish the issue (ZF-3078) I opened regarding bringing Cache-Control functionalitiy to the Page cache.

Good job going to the source for information that no one could have gleaned from the documentation.

@Eric: Cache lifetime is largely irrelevant since a static cache “hit” will bypass PHP entirely. Therein lies it’s great advantage, and great disadvantage (no auto-expiry). If you need to time expiration, you can use a cron task to monitor collections of static files based on their cached tag references and modification times.

@Mary: There’s a few ways of keeping cleaning efficient. Specific tagging (avoiding generalised tagging) can keep a tidier breakdown of the cache in the first place, esp. between time sensitive caches (must be cleaned almost immediately if data alters) and time insensitive caches (cleaning can be deferred to a cron process).

Another tip (with some extra coding), depending on your setup, is that in some scenarios you can take advantage of a light web server (e.g. Nginx) which can interact with memcached. Not all “static” caches need be stored to files though it’s the most common need on single server apps. Whenever Zend_Cache is refactored for ZF 2.0, and we have some cleanly defined interfaces (static caching uses a couple of “workarounds” which is why it seems odd when using it outside of the cache action helper), it’s something I’ll look into porting in directly for support.

Thanks to Brandon for the light shedding article! Great one, as usual.

Mary, what I do is set very high, basically unlimited expire times, then prime the cache via cron, which overwrites cache files instead of dealing w/ cleaning out expiring caches.

http://framework.zend.com/issues/browse/ZF-3076

It must not be used to cache a HTTP redirect or under any error condition as it cannot know the HTTP status that was sent, and essentially means any page is cached, and later served as HTTP 200 OK.

The workaround is to call the $cache->cancel() on these conditions manually.

However I’ve not delved deep into the new cache helper, I can’t see any explicit code that handles these conditions.

I’ve tryied on my web page but still have a problem, do you know if there is any way to change the cache lifetime for a specific action?

Thanks.

Cleaning up static caches has been a problem for me. Watch out for the automated “cleans” that the cache system will do every so many cache requests. If you have pages that expire, these will all require disk access. Now that you have cached lots of your requests, cleans do not happen as often. When a clean occurs it will slow down the request dramatically. The problem with this is that you will not notice for a while as it does not slow down every request. Only ones when the cleans randomly(?) occur.

You are better off disabling the Zend_Cache cleaning mechanism and scripting it into a cron job that executes it on your website’s quiet times.

I am sure with some profiling you will see what I mean. That or if have lots of static cache pages, expire your static cache pages and are on a shared webhost, look for the timeouts in your log files.

Also if Google bot can access your static cache pages, it will crawl them all one after another, just to make sure that they all expire at the same time.

Zend_Db_Table_Abstract::setDefaultMetadataCache($cache);

Where $cache is your factory-generated cache object.