<short>caches generated content on disk if an etag response header is set; if the backend sends an already cached etag, the backend is closed and the file is sent directly.</short>
<description>
<textile>
Please note: This will not skip the backend, as it will need at least the reponse headers.
*Hint:*
Use a cron-job like the following to remove old cached data, e.g. in crontab daily:
<short>cache responses based on the ETag response header</short>
<parametername="path">
<short>directory to store the cached results in</short>
</parameter>
<description>
This blocks action progress until the response headers are done (i.e. there has to be a content generator before it (like fastcgi/dirlist/static file).
You could insert it multiple times of course (e.g. before and after deflate).