Hi, I presume from your description you're enforcing https-only in your code? Cronjobs don't actually use HTTP, so they simply fill in the protocol value with a default of 'http'. You need to exempt cron requests in your app from sending 302s.
-Nick Johnson On Sat, Feb 6, 2010 at 1:15 AM, lent <[email protected]> wrote: > Hi, > > I have an (java) application that's secured so that only https access > is allowed. I'm running into a problem with cron jobs in that they > are sent using http and when scheduled request hits my app gets > redirected to https and and winds up getting "too many continues" and > 302 status. I didn't find anything in the docs about configuring to > have the scheduled requests sent via https. Is this in the plans? > Any suggestions for how I can get around this problem other than to > have the scheduled request urls be allowed to come in through http. > > Thanks, > Len > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
