Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains
In case you hadn't seen this, I'm sure you'll be happy to know that SSL is now in Trusted Tester: http://groups.google.com/group/google-appengine/browse_thread/thread/d7fb200cbe9d2010# I DID say we were going to release this as soon as possible and, well, here we are :) Greg On Sat, Oct 15, 2011 at 8:03 PM, jon jonni.g...@gmail.com wrote: +1 On Oct 14, 8:07 pm, Louis Le Coeur louis.leco...@gmail.com wrote: 1.5.5 SDK release and still no mention of SSL whatsoever... It seems now certain that we won't have it by the end of the year. And it's starting to get really frustrating, at a time where browser support is ubiquitous enough for an SNI-only solution. When I see all of their other announcements, I can't help thinking : 99.95% SLA? conversion API? but why on earth do they even work on this? why don't they put 100% of their resources on SSL? Do they listen to us at all? And it's a shame because we'd certainly be able to appreciate their otherwise excellent work if they solved this bottleneck. *When you send a rocket to the moon, focus on the engine first, not the leather seats.* -- 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. -- 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.
Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains
Brandon is both right and wrong. I'd suggest you take his comments with a bit of a grain of salt since he starting a fledging CloudFlare-like service called CDN In A Box. The short answer is: CloudFlare today will not hurt your SEO (and in fact usually helps it fairly significantly) and provides a high availability solution to the AppEngine SSL problem. Here's the longer answer: When CloudFlare first began, we did have challenges with Google's crawler. While Brandon's reasoning may seem sound, it's actually an incorrect diagnosis. It was a puzzle for us for a while until we learned what the actual issue was by talking directly with the head of the Google Crawl team. At the root of the problem is the fact that Google sets crawl velocity based on an IP address. If multiple sites share an IP address and one of them has an issue then Google turns down crawl velocity in order to make sure they aren't contributing to excess load on the server that may be causing the problem. CloudFlare clusters multiple sites behind a pool of IP addresses. If one of those sites has an issue, we faithfully pass through the server error response code. Google's crawler was picking up that error response code and turning down crawl velocity for all the sites using that IP address. As a result, sites that weren't having issues but shared a CloudFlare IP with sites that were had their crawl rates decreased and therefore their SEO hurt. Google's crawl team had seen this problem before with other major CDNs like Akamai. The way they had dealt with it there was by detecting the CDN's CNAME in the DNS chain and writing a special rule for the crawler. In our case, a CloudFlare CNAME would not always appear in the DNS chain since we may return an IP address of our proxies directly as an A Record, so the solution for other CDNs would not work. We worked directly with the Google crawl team, as well as the crawl teams from other major search providers, in order to come up with a solution. Today, there are special rules in place for CloudFlare's IP ranges that assign the highest crawl velocity to sites using the IPs. We have an established channel to feed new CloudFlare IPs to the crawl teams as we are allocated them. You can see this yourself if your site is behind CloudFlare by logging in to Google Webmaster Tools and seeing that the option to adjust your crawl rate is no longer available. Search engines know we can handle their maximum crawl load, so they hammer away at us -- which is great for our users. While Brandon is correct that this was a problem before, our work with search crawl teams turned this problem into a feature and it is part of the reason why today being on CloudFlare can help your overall SEO. If you're interested in learning more, I've written about this on our blog: http://blog.cloudflare.com/cloudflare-and-seo And, related: http://blog.cloudflare.com/losing-seo-link-juice-to-traditional-cdns In terms of SSL and AppEnginehttp://blog.cloudflare.com/ssl-on-custom-domains-for-appengine-and-other, we had a number of users ask if we could help. We spent a significant amount of time building a cloud-based solution that allowed for custom domains to have SSL. Since we'd already built the frontend of that, it was relatively easy for us to extend the solution to the backend and, essentially, mask AppEngine's non-custom domain with your own custom domain. It was minor feature for us, but we've been surprised by how many AppEngine users have adopted it. Today, CloudFlare powers more than 100,000 websites. We typically will double the performance of a site and add a security layer which you can enable or disable depending on your preferences. If there are ways in which we can make CloudFlare better for the AppEngine community, please don't hesitate to let us know. Cheers, Matthew Prince CEO, CloudFlare @eastdakota https://twitter.com/#!/eastdakota -- 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/-/XNFWzT0YH3gJ. 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.
Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains
I work at CloudFlare, to make my biases crystal clear. Our service is not harmful to SEO. Here's two blog posts on the topic: http://blog.cloudflare.com/cloudflare-and-seo http://blog.cloudflare.com/losing-seo-link-juice-to-traditional-cdns Brandon, I'm surprised by your assertions, which don't reflect the reality of the more than 100,000 websites using CloudFlare today. We're serving more than 15 billion pageviews/month to more than 350 million unique users/month for our customers' websites. Brandon, I hope you've shared your background with this audience, so your biases are similarly clear. On the original topic of this thread -- as posts in issue 792 show, we took steps in July to make SSL available to GAE customers, and we'll continue to do so. We're not a host, and don't see GAE as competition. When GAE offers SSL, customers can still benefit from a global CDN with security by using CloudFlare in conjunction with GAE. If there are any CloudFlare specific questions, happy to answer them. John Roberts first name at cloudflare dot com -- 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/-/bEf1AzSq1SkJ. 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.
Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains
Take Brandon's comments with a bit of a grain of salt given that he's trying to launch a CloudFlare-like competitor called CDN in a Box. Here's info on CloudFlare and SEO addressing his speculated concerns: http://blog.cloudflare.com/cloudflare-and-seo Short summary: we actually markedly improve most sites' SEO and can help AppEngine users get SSL on a custom domain. As to the topic at hand, a number of users requested that we provide a way to allow SSL on AppEngine. We added a simple feature to support it and have been surprised how many people have taken advantage of it. Implementing SSL in a cloud-based environment is non-trivial and we spent more than a year, had to form several key partnerships, and developed significant technology, in order to get it to work reliably before we launched CloudFlare. If there are further ways we can help the AppEngine developer community, let us know. Matthew Prince CEO, CloudFlare @eastdakota http://twitter.com/#!/eastdakota -- 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/-/_Wllc7sraMMJ. 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.
Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains
Thank you for taking the time to explain the details. Jeff On Sat, Sep 24, 2011 at 2:36 PM, Matthew Prince matt...@cloudflare.com wrote: Brandon is both right and wrong. I'd suggest you take his comments with a bit of a grain of salt since he starting a fledging CloudFlare-like service called CDN In A Box. The short answer is: CloudFlare today will not hurt your SEO (and in fact usually helps it fairly significantly) and provides a high availability solution to the AppEngine SSL problem. Here's the longer answer: When CloudFlare first began, we did have challenges with Google's crawler. While Brandon's reasoning may seem sound, it's actually an incorrect diagnosis. It was a puzzle for us for a while until we learned what the actual issue was by talking directly with the head of the Google Crawl team. At the root of the problem is the fact that Google sets crawl velocity based on an IP address. If multiple sites share an IP address and one of them has an issue then Google turns down crawl velocity in order to make sure they aren't contributing to excess load on the server that may be causing the problem. CloudFlare clusters multiple sites behind a pool of IP addresses. If one of those sites has an issue, we faithfully pass through the server error response code. Google's crawler was picking up that error response code and turning down crawl velocity for all the sites using that IP address. As a result, sites that weren't having issues but shared a CloudFlare IP with sites that were had their crawl rates decreased and therefore their SEO hurt. Google's crawl team had seen this problem before with other major CDNs like Akamai. The way they had dealt with it there was by detecting the CDN's CNAME in the DNS chain and writing a special rule for the crawler. In our case, a CloudFlare CNAME would not always appear in the DNS chain since we may return an IP address of our proxies directly as an A Record, so the solution for other CDNs would not work. We worked directly with the Google crawl team, as well as the crawl teams from other major search providers, in order to come up with a solution. Today, there are special rules in place for CloudFlare's IP ranges that assign the highest crawl velocity to sites using the IPs. We have an established channel to feed new CloudFlare IPs to the crawl teams as we are allocated them. You can see this yourself if your site is behind CloudFlare by logging in to Google Webmaster Tools and seeing that the option to adjust your crawl rate is no longer available. Search engines know we can handle their maximum crawl load, so they hammer away at us -- which is great for our users. While Brandon is correct that this was a problem before, our work with search crawl teams turned this problem into a feature and it is part of the reason why today being on CloudFlare can help your overall SEO. If you're interested in learning more, I've written about this on our blog: http://blog.cloudflare.com/cloudflare-and-seo And, related: http://blog.cloudflare.com/losing-seo-link-juice-to-traditional-cdns In terms of SSL and AppEngine, we had a number of users ask if we could help. We spent a significant amount of time building a cloud-based solution that allowed for custom domains to have SSL. Since we'd already built the frontend of that, it was relatively easy for us to extend the solution to the backend and, essentially, mask AppEngine's non-custom domain with your own custom domain. It was minor feature for us, but we've been surprised by how many AppEngine users have adopted it. Today, CloudFlare powers more than 100,000 websites. We typically will double the performance of a site and add a security layer which you can enable or disable depending on your preferences. If there are ways in which we can make CloudFlare better for the AppEngine community, please don't hesitate to let us know. Cheers, Matthew Prince CEO, CloudFlare @eastdakota -- 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/-/XNFWzT0YH3gJ. 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.
RE: [google-appengine] Re: calling out the app engine team on ssl for custom domains
I have said multiple times our customers don't align at all, and we started CDN in a Box as a result of the needs of clients who were experiencing issues with CF. CiaB doesn't do SSL at all. My concerns aren't speculated. http://www.google.com/#sclient=psy-ab http://www.google.com/#sclient=psy-abhl=ensource=hpq=%22This+restriction +will+disappear+when+no+more+harmful+behavior+is+detected.%22pbx=1oq=%22Th is+restriction+will+disappear+when+no+more+harmful+behavior+is+detected.%22 aq=faqi=aql=1gs_sm=egs_upl=18730l20344l2l20823l hl=ensource=hpq=%22This+restriction+will+disappear+when+no+more+harmful+b ehavior+is+detected.%22pbx=1oq=%22This+restriction+will+disappear+when+no+ more+harmful+behavior+is+detected.%22aq=faqi=aql=1gs_sm=egs_upl=18730l2 0344l2l20823l3l3l0l0l0l0l91l149l2l2l0bav=on.2,or.r_gc.r_pw.r_cp.fp=4434126 5e68b94f2biw=1021bih=567 Check out all of these sites that CF has presented the Captcha to Google Crawler. Do this twice and all of a sudden that ranking you had for Ice cream San Francisco goes away. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Matthew Prince Sent: Saturday, September 24, 2011 8:16 PM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains Take Brandon's comments with a bit of a grain of salt given that he's trying to launch a CloudFlare-like competitor called CDN in a Box. Here's info on CloudFlare and SEO addressing his speculated concerns: http://blog.cloudflare.com/cloudflare-and-seo Short summary: we actually markedly improve most sites' SEO and can help AppEngine users get SSL on a custom domain. As to the topic at hand, a number of users requested that we provide a way to allow SSL on AppEngine. We added a simple feature to support it and have been surprised how many people have taken advantage of it. Implementing SSL in a cloud-based environment is non-trivial and we spent more than a year, had to form several key partnerships, and developed significant technology, in order to get it to work reliably before we launched CloudFlare. If there are further ways we can help the AppEngine developer community, let us know. Matthew Prince CEO, CloudFlare @eastdakota http://twitter.com/#!/eastdakota -- 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/-/_Wllc7sraMMJ. 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.
RE: [google-appengine] Re: calling out the app engine team on ssl for custom domains
And I should clarify. Putting Facebook.Yourdomain.com on CF for https requests from Facebook, (leaving the rest of the application running not on CF) is probably not a horrible idea. You'd only be putting user experience at risk if a captcha appeared or CF throttled the connection in a strange way, not your entire site. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Brandon Wirtz Sent: Monday, September 26, 2011 12:39 PM To: google-appengine@googlegroups.com Subject: RE: [google-appengine] Re: calling out the app engine team on ssl for custom domains I have said multiple times our customers don't align at all, and we started CDN in a Box as a result of the needs of clients who were experiencing issues with CF. CiaB doesn't do SSL at all. My concerns aren't speculated. http://www.google.com/#sclient=psy-ab http://www.google.com/#sclient=psy-abhl=ensource=hpq=%22This+restriction +will+disappear+when+no+more+harmful+behavior+is+detected.%22pbx=1oq=%22Th is+restriction+will+disappear+when+no+more+harmful+behavior+is+detected.%22 aq=faqi=aql=1gs_sm=egs_upl=18730l20344l2l20823l hl=ensource=hpq=%22This+restriction+will+disappear+when+no+more+harmful+b ehavior+is+detected.%22pbx=1oq=%22This+restriction+will+disappear+when+no+ more+harmful+behavior+is+detected.%22aq=faqi=aql=1gs_sm=egs_upl=18730l2 0344l2l20823l3l3l0l0l0l0l91l149l2l2l0bav=on.2,or.r_gc.r_pw.r_cp.fp=4434126 5e68b94f2biw=1021bih=567 Check out all of these sites that CF has presented the Captcha to Google Crawler. Do this twice and all of a sudden that ranking you had for Ice cream San Francisco goes away. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Matthew Prince Sent: Saturday, September 24, 2011 8:16 PM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains Take Brandon's comments with a bit of a grain of salt given that he's trying to launch a CloudFlare-like competitor called CDN in a Box. Here's info on CloudFlare and SEO addressing his speculated concerns: http://blog.cloudflare.com/cloudflare-and-seo Short summary: we actually markedly improve most sites' SEO and can help AppEngine users get SSL on a custom domain. As to the topic at hand, a number of users requested that we provide a way to allow SSL on AppEngine. We added a simple feature to support it and have been surprised how many people have taken advantage of it. Implementing SSL in a cloud-based environment is non-trivial and we spent more than a year, had to form several key partnerships, and developed significant technology, in order to get it to work reliably before we launched CloudFlare. If there are further ways we can help the AppEngine developer community, let us know. Matthew Prince CEO, CloudFlare @eastdakota http://twitter.com/#!/eastdakota -- 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/-/_Wllc7sraMMJ. 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. -- 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.
RE: [google-appengine] Re: calling out the app engine team on ssl for custom domains
In case that Google link didn't make sense. That's 2500 sites (2.5% of CF's Site base) that have had their site present Google bot with an access denied error. Not with a 500 error, Not with a 403. With a perfectly happy 200. As to my loyalties and background. CDNinaBox runs on GAE. I'm not likely to make any money selling it to GAE users. Currently CDN In A Box has 150-ish Domains running on it. Our typical customer is on the service less than 90 days before we move them to a bigger solution, or resolve their issues. The sites that are on longer are small sites that aren't looking to scale. CDN in a Box does NOT view CF as a competitor, we do view them as a lead generator for our SEO services at BlackWaterOps.com in fact, we would make the most money if more people would join Cloud Flare. And when comparing our bias, consider that CF only shows up in this forum when they want to bash me, bash GAE, or claim they handle Proxies correctly and that GAE treats them unfarely. I'm here every day. Multiple times a day, and have maybe promoted my products or services 10 times, and those were for people who were considering building what I already had built, not because I was going to get rich on $20 a month. (I can't even make that back on the 45 minute call I have with most of those people to help them figure out their issues). Brandon Wirtz BlackWaterOps: President / Lead Mercenary Description: http://www.linkedin.com/img/signature/bg_slate_385x42.jpg Work: 510-992-6548 Toll Free: 866-400-4536 IM: drak...@gmail.com (Google Talk) Skype: drakegreene http://www.blackwaterops.com/ BlackWater Ops From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Brandon Wirtz Sent: Monday, September 26, 2011 12:39 PM To: google-appengine@googlegroups.com Subject: RE: [google-appengine] Re: calling out the app engine team on ssl for custom domains I have said multiple times our customers don't align at all, and we started CDN in a Box as a result of the needs of clients who were experiencing issues with CF. CiaB doesn't do SSL at all. My concerns aren't speculated. http://www.google.com/#sclient=psy-ab http://www.google.com/#sclient=psy-abhl=ensource=hpq=%22This+restriction +will+disappear+when+no+more+harmful+behavior+is+detected.%22pbx=1oq=%22Th is+restriction+will+disappear+when+no+more+harmful+behavior+is+detected.%22 aq=faqi=aql=1gs_sm=egs_upl=18730l20344l2l20823l hl=ensource=hpq=%22This+restriction+will+disappear+when+no+more+harmful+b ehavior+is+detected.%22pbx=1oq=%22This+restriction+will+disappear+when+no+ more+harmful+behavior+is+detected.%22aq=faqi=aql=1gs_sm=egs_upl=18730l2 0344l2l20823l3l3l0l0l0l0l91l149l2l2l0bav=on.2,or.r_gc.r_pw.r_cp.fp=4434126 5e68b94f2biw=1021bih=567 Check out all of these sites that CF has presented the Captcha to Google Crawler. Do this twice and all of a sudden that ranking you had for Ice cream San Francisco goes away. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Matthew Prince Sent: Saturday, September 24, 2011 8:16 PM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains Take Brandon's comments with a bit of a grain of salt given that he's trying to launch a CloudFlare-like competitor called CDN in a Box. Here's info on CloudFlare and SEO addressing his speculated concerns: http://blog.cloudflare.com/cloudflare-and-seo Short summary: we actually markedly improve most sites' SEO and can help AppEngine users get SSL on a custom domain. As to the topic at hand, a number of users requested that we provide a way to allow SSL on AppEngine. We added a simple feature to support it and have been surprised how many people have taken advantage of it. Implementing SSL in a cloud-based environment is non-trivial and we spent more than a year, had to form several key partnerships, and developed significant technology, in order to get it to work reliably before we launched CloudFlare. If there are further ways we can help the AppEngine developer community, let us know. Matthew Prince CEO, CloudFlare @eastdakota http://twitter.com/#!/eastdakota -- 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/-/_Wllc7sraMMJ. 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
Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains
That's a great list that actually doesn't prove what you think, but it does turn out to prove one of CloudFlare's value propositions. If you look down the list you'll find that a majority are *.blogspot.com domains. By definition, since blogspot.com users can't subdeligate the DNS of blogspot.com subdomains, they cannot be on CloudFlare. So what are they? Turns out they're pages that web scrapers have pulled from our customers' sites that we've blocked. The content farmer scrapers have then recreated our challenge page on free services like Blogspot. In other words, these aren't CloudFlare's customers, they're people trying to steal content from CloudFlare's customers that we've stopped. Awesome! I did find a small handful of actual CloudFlare customers on that list. I dug into them further. While I can't explain their rationale, they've all explicitly blocked Google's crawler from visiting their site, an odd preference we've helped them enforce. I can't find a single example of a challenge page where we've misclassified the Google crawler which makes sense since we've worked directly with the Google crawl team to make sure our service plays well with them. -- 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/-/1e-vlTAtp44J. 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.
Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains
I too wonder about the availability of cloud fare. I'd like to find out how it goes for you if you end up using it. Steve On 11-09-24 02:48 PM, johnP wrote: Jeff - thanks for the link to Cloudflare. It certainly seems like an interesting option. The risk with implementing them is that it's one more layer that can fail. Does anyone else have feedback about how well it works?Also, does anyone have thoughts on whether the other benefits of Cloudflare (edge-caching and security layer) is relevant to Appengine users, is it essentially redundant? On Sep 23, 2:50 am, Jeff Schnitzerj...@infohazard.org wrote: Try this out: http://blog.cloudflare.com/ssl-on-custom-domains-for-appengine-and-other When our business is ready to launch, this is our intended plan for always-SSL for our app. Cloudflare does edge caching for all content too - possibly better than Google's (wholly undocumented and not guaranteed) edge cache. I hate to plug a solution that I haven't tried yet, but it looks promising. Try it out and let me know, or you can wait for my report towards the end of the year. Jeff -- 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.
RE: [google-appengine] Re: calling out the app engine team on ssl for custom domains
You will be most unhappy. Many of my SEO clients are FORMER cloudflare users who found out the hard way that when Cloudflare mistakes Google Bot for a DDoS Attack they get delisted, or when one of Google's Human Quality validation techs visit the site and get a captcha challenge they get Delisted. Cloudflare also has issues that because adult sites often use it, that they get blocked by large organizations firewall. -Original Message- From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Steve Sherrie Sent: Saturday, September 24, 2011 11:51 AM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains I too wonder about the availability of cloud fare. I'd like to find out how it goes for you if you end up using it. Steve On 11-09-24 02:48 PM, johnP wrote: Jeff - thanks for the link to Cloudflare. It certainly seems like an interesting option. The risk with implementing them is that it's one more layer that can fail. Does anyone else have feedback about how well it works?Also, does anyone have thoughts on whether the other benefits of Cloudflare (edge-caching and security layer) is relevant to Appengine users, is it essentially redundant? On Sep 23, 2:50 am, Jeff Schnitzerj...@infohazard.org wrote: Try this out: http://blog.cloudflare.com/ssl-on-custom-domains-for-appengine-and-ot her When our business is ready to launch, this is our intended plan for always-SSL for our app. Cloudflare does edge caching for all content too - possibly better than Google's (wholly undocumented and not guaranteed) edge cache. I hate to plug a solution that I haven't tried yet, but it looks promising. Try it out and let me know, or you can wait for my report towards the end of the year. Jeff -- 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. -- 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.
Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains
There ya go then. Steve On 11-09-24 03:31 PM, Brandon Wirtz wrote: You will be most unhappy. Many of my SEO clients are FORMER cloudflare users who found out the hard way that when Cloudflare mistakes Google Bot for a DDoS Attack they get delisted, or when one of Google's Human Quality validation techs visit the site and get a captcha challenge they get Delisted. Cloudflare also has issues that because adult sites often use it, that they get blocked by large organizations firewall. -Original Message- From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Steve Sherrie Sent: Saturday, September 24, 2011 11:51 AM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Re: calling out the app engine team on ssl for custom domains I too wonder about the availability of cloud fare. I'd like to find out how it goes for you if you end up using it. Steve On 11-09-24 02:48 PM, johnP wrote: Jeff - thanks for the link to Cloudflare. It certainly seems like an interesting option. The risk with implementing them is that it's one more layer that can fail. Does anyone else have feedback about how well it works?Also, does anyone have thoughts on whether the other benefits of Cloudflare (edge-caching and security layer) is relevant to Appengine users, is it essentially redundant? On Sep 23, 2:50 am, Jeff Schnitzerj...@infohazard.org wrote: Try this out: http://blog.cloudflare.com/ssl-on-custom-domains-for-appengine-and-ot her When our business is ready to launch, this is our intended plan for always-SSL for our app. Cloudflare does edge caching for all content too - possibly better than Google's (wholly undocumented and not guaranteed) edge cache. I hate to plug a solution that I haven't tried yet, but it looks promising. Try it out and let me know, or you can wait for my report towards the end of the year. Jeff -- 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. -- 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.
