No, they say that, but many of their headers have private IP ranges, reciprocal IP's, and other issues. They have a hacked together product running on borrowed infrastructure, I make a LOT of money cleaning up after them.
And I feel bad because most the people who end up getting burned by them can't afford it. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Owen Wiggins Sent: Saturday, September 24, 2011 8:44 PM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] CloudFlare https traffic blocked? Thank you for your quick reply, Brandon! I believe CloudFlare uses the "industry standard X-Forwarded-For header": http://code.google.com/appengine/forum/?place=msg%2Fgoogle-appengine%2F4D1IG qCh4LA%2FrguR4Zqtj08J We're not seeing excessive traffic this week either - not sure what would be considered a possible DDoS by Google, though. Regardless, I'm really in a tough spot here and would love an alternative if anyone can suggest something. I'm sure many other developers are in a similar position... -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/cRtKFojKcBMJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
