This seems to be related to the update of the URLFetch that was done in past october and has been enforced recently.
Affected users should have received an email about it. On Thursday, February 12, 2015 at 8:00:47 AM UTC+1, Vinny P wrote: > > On Tue, Feb 10, 2015 at 1:30 PM, Greg Tracy wrote: > >> I have an old app that has been re-directing traffic to another App >> Engine app for a couple of years. It just stopped working this morning. The >> re-directs return 404s. Going directly to the re-direct location works >> correctly, however. >> >> Is there any indication that there is an infrastructure problem? The >> re-direct appears to work from the logs in the original app. >> > > > > How did you configure the redirect? Is your application issuing a 30x > redirect, or are you using the built-in redirect from the HRD migration > <https://cloud.google.com/appengine/docs/adminconsole/migration>? > > If your application is redirecting using a status code, can you look at > the response sent to the client (for instance, look at it using Chrome's > developer tools) and see what the response looks like? > > > ----------------- > -Vinny P > Technology & Media Consultant > Chicago, IL > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/8629351e-6e28-4007-b42c-abca3187809a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
