I think there is still a bug on the purging webservice, I think the
object remains in memcache. Until I find a fix and release it in the
next version, you could try to flush the object manually by doing a
request using curl like this:
$ curl -X DELETE http://your.domain.tld/path/to/file.js
After that, you can also try to flush memcached objects to ensure
getting rid of any stale content:
$ curl -X DELETE http://your.domain.tld/<base url>/__ALL__\?memcache
You should receive the message "Memcache flushed.".
Let me know about that.
Best,
Samuel
> --
> Project page: http://code.google.com/p/cirruxcache/
> News: http://www.shad.cc/tag/cirruxcache
> Groups: http://groups.google.com/group/cirruxcache
>
--
Samuel Alba
To do that, fill the variable named "allowFlushFrom" to your IP
following the form below:
allowFlushFrom = ['x.x.x.x']
(replace with your public ip from whatismyip.com for instance).
You can read http://code.google.com/p/cirruxcache/wiki/PoP for more details.
Yes the commands need to be executed from your local shell ;)
Try to do it, and if you fail, please copy/paste your app.py config
(only PoP section will be enough, adding your url mapping), and the
executed curl commands.
Let me know.
Sam
Let me know if you have another idea to implement.
On Fri, Feb 11, 2011 at 3:02 AM, Zuko <zack...@gmail.com> wrote:
> May be we can have something like...
>
> http://appname.appspot.com/path/to/file.js?request=del&key=secretkey
>
>
> On Jul 29 2010, 4:32 pm, Samuel Alba <sam.a...@gmail.com> wrote:
>> You need to explicitly authorized your IP to send DELETE request.
>>
>> To do that, fill the variable named "allowFlushFrom" to your IP
>> following the form below:
>> allowFlushFrom = ['x.x.x.x']
>>
>> (replace with your public ip from whatismyip.com for instance).
>>
>> You can readhttp://code.google.com/p/cirruxcache/wiki/PoPfor more details.
--
Samuel Alba
@sam_alba