This is a mirror of the conversation from 9 months ago and the one from 9 months before that, and the conversation on the Amazon forum, and the Rackspace forum and the Google Webmasters forum...
https://groups.google.com/forum/#!msg/google-appengine/om1DF_61Xl4/cRtKFojKc BMJ http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CFgQFjAB &url=http%3A%2F%2Fproductforums.google.com%2Fd%2Ftopic%2Fwebmasters%2FsILDRV zPo6U&ei=38cZUMO_L4mMqwGk6oCICg&usg=AFQjCNHk6YVJTj6-hj_2NYP1OBBIuSFQXw&sig2= dRQ9_wSJ8bDC4nzzS6IQVQ CF does headers wrong. CF doesn't play well with Google bot. Not news to anyone. CF "Double wraps" its proxy some times. Don't know why. When this happens Google Freaks. CF doesn't report what IP the request is made on behalf of sometimes. Google Freaks out. CF reports that it is proxying on behalf of a Google Internal IP sometimes GOOGLE REALLY FREAKS OUT. You guys can be assholes, but I'm telling you where your problem is. I told you 2 years ago, I told you 9 months ago. I am telling you now. You can stick your fingers in your ears, but this is not Google doing the wrong thing, it is CF. You won't have this problem if you use Akamai's DSA/PLC solution. Which is what I would recommend to anyone who needs international access on GAE, or who wants to leverage enterprise class caching. It's what we are using for our top tier deployments. -- 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.
