/_cron/expired

[ahwebd]

Hello,
Thanks for all the work,

When I check my apache server access log, I find :
/_cron/expired HTTP/1.1" 404 2494 "-" "CirruxCache 0.2.2 / shad
(http://code.google.com/p/cirruxcache/) ;

It looks like CirruxCache is requesting the path "/_cron/expired" from
my server, but it gets 404 errors, can you explain this problem and
how to resolve it

Best Regards

[Samuel Alba]

Hello,

I think this is due to your URL mapping. In this case /_cron/ URL is
mapped to a cache service, so CirruxCache forwards the request to your
origin, that's the problem. For a quick fix, I invite you to use the
last version (0.4.1): with this version, cron mapping is included
automatically, avoiding this kind of error.

- Sam

> --
> Project page: http://code.google.com/p/cirruxcache/
> News: http://www.shad.cc/tag/cirruxcache
> Groups: http://groups.google.com/group/cirruxcache
>

--
Samuel Alba

[ahwebd]

I downloaded the new version, there is inside the file "cron.yaml"
which also contains:
url: /_cron/expired

I don't have this path on my server, so how am I supposed to configure
this file

Regards

[Samuel Alba]

You don't have to! /_cron/expired won't reach your origin server. This
is an internal URL used by CirruxCache. More briefly: don't touch it
if you don't understand the purpose.

Best,

- Sam

[ahwebd]

I resolved the issue by adding "'/_cron/(.*)', 'Cron'," to
"urls['default']" section. before this I had all paths (including /
_cron/(.*) ) directed to my custom POP, now I have the following on my
config.py :

urls['default'] = (
'/_cron/(.*)', 'Cron',
'(/.*)', 'config.Static'
)

Thanks a lot Samuel

[Samuel Alba]

This is a good idea only if you are still on the old version (before 0.4.1).

[ahwebd]

I'm using version 0.4.1

Yup, I removed the added line now and still the /_cron/* paths handled
internally

Thanks a lot for the help