[google-appengine] Re: GAE, App Engine Patch, CRON (301) Issues

2009-09-18 Thread bbayer
Hi, Same problem and I have solved it by changing my django's url pattern and updating both cron and app.yml files. Here is the solution. Django tries to add "/" if you are not using it on end of url. It does that by using Http 301(permanent redirect). It seems app engine code changed to disallow

[google-appengine] Re: GAE, App Engine Patch, CRON (301) Issues

2009-09-17 Thread ttk
Hi Nick, Thanks for the response. 1. The only thing in my app.yaml that has a login is: handlers: - url: /remote_api script: $PYTHON_LIB/google/appengine/ext/remote_api/handler.py secure: optional login: admin Is that why 301 is coming up because GAE is checking the user and redirecting

[google-appengine] Re: GAE, App Engine Patch, CRON (301) Issues

2009-09-17 Thread Nick Johnson (Google)
Hi ttk, On Tue, Sep 15, 2009 at 11:11 PM, ttk wrote: > > Hello, > > I'm wondering if anyone is having similar issues with GAE cron jobs / > tasks via App Engine Patch? > > Intended Flow: > 1. Cron job 'do/store/weekly' triggers the creation of a task to build > html email. > 2. Task executes, bu