Cron URLs Receive 403 Status in a Flexible Environment

Question

We are experimenting with a flexible environment and we want to migrate an existing application. Everything seems to be going well except for cron entries.

We have a bunch of cron, and each url is protected as admin "(as indicated in the documentation), but every time the URL goes to the cron service, we get 403 status, if the URL goes to the user through the browser everything works fine.

In a standard environment, everything is fine.

Is there anything we can check?

Answer 1

I assume that you added login: admin to the app.yaml handler section to protect the cron service in the standard Google App Engine environment.

But in the Engine flex application, he changed the way he protects your cron handlers like this (PHP example):

Check $ _SERVER ['HTTP_X_APPENGINE_CRON'], and if it is true, requests come from the cron service of the App Engine application.