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,
+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
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
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
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
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
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
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
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
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
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
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
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
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
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
15 matches
Mail list logo