The headers would be coming from nginx. Unless nginx is passing along malformed headers, it wouldn't be caused by us.
"CF does headers wrong" Please provide something specific that is malformed. We're more than happy to check on it both internally and with nginx. To date, you just keep making claim after claim without providing anything to substantiate it. "CF doesn't play well with Google bot" Also incorrect. We have hundreds of thousands of sites using us without issue. In addition, crawl errors that people write on the forums may or may not be related to CloudFlare and we do investigate these complaints. Things that could go wrong with crawling (a small sample): 1. user changed something in robots.txt recently 2. bad .htacess rules 3. security plugins (not CloudFlare) blocking googlebot If we find an issue that we're absolutely causing, we fix it. If we find that we're having a problem with a service (like Google today), then we reach out to them to find out what the issue is and fix it. The internet is a big place & a lot of things can happen that are not to blame on any one company. I'm sure some of your customers have issues with your service as well that may/may not be related to your product I don't jump in and go: "SEEEEE (done on purpose) what can go wrong when you use XYZ?" I also don't make any claims about how your service works or any other weakness in your product. That is the absolute worst way to market your product. On Wed, Aug 1, 2012 at 5:29 PM, Drake <[email protected]> wrote: > 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. > -- 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.
