Hi, I ran into this issue as well. As a slight improvement I would suggest to invalidate cached 404 responses weekly. That would be in the spirit of #625458 (the reason for caching 404 in the first place). In addition implementing this workaround is very easy. One can simply add the following lines to /etc/cron.weekly/approx within the "if":
find /var/cache/approx -empty -type f -perm 0000 -delete find /var/cache/approx -empty -type d -mindepth 1 -delete After applying this, the weekly cron job will invalidate all cached 404 responses. Thus the cache will become self-healing from outdated 404 responses. This workaround might even qualify for inclusion into wheezy. Helmut -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
