' This would be possible that the preloader is making more requests at rate that appengine either can't keep up with or triggers a "rate limiting" security rule. '
This is the reply from CloudFlare Not that I don't like CloudFlare, but is there anyone using CloudFlare only for the DNS/ naked domain to www. redirect feature? I'm thinking of going the manual SSL route with appengine and using cloudflare only for the redirect, which is extremely useful (Another plus is that, appengine provides an approximate user lat,lon value in the header, which is extremely useful as a default value :) On Tuesday, October 15, 2013 10:31:59 AM UTC+3, Kaan Soral wrote: > > The issue stopped right after I disabled "Website Preloader" on CF, might > be coincidental with a low probability > > CF didn't reply to the ticket > > interesting turn of events > > On Tuesday, October 15, 2013 10:02:35 AM UTC+3, Richard Watson wrote: >> >> Did you get any joy? Find anything out from CF? >> >> On Sunday, October 13, 2013 7:12:50 PM UTC+2, Kaan Soral wrote: >>> >>> I've enabled warmup requests to see whether it would change anything >>> After deploying changes, all instances were killed, as expected >>> >>> I've waited some instanced to spin up, they didn't >>> Then I visited the app from the cloudflare url, and instances still >>> didn't spin up, I got a 520 CF error again >>> >>> Then I visited the app through the *.appspot.com url, and an instance >>> spinned up to serve the request >>> >>> So I think the issue might be with appengine, not responding to CF >>> requests >>> >> -- 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. For more options, visit https://groups.google.com/groups/opt_out.
