News for hackers. Stuff that matters.

pencoyd

Re:Cloudflare Traffic Manager on Thursday September 29, 2016 @01:03PM (#12606897)
I hope you'll apply for Early Access and put our new service through its paces.

A colleague just published more details here https://blog.cloudflare.com/cloudflare-traffic-manager-the-d...

Re:Everybody gets WebSockets on Thursday May 05, 2016 @11:32PM (#11641496)
As you know, when terminating a WebSocket connection due to releases CloudFlare now signals this action to both client and origin server by sending the 1001 status code (aka "going away", see section 7.4.1 of RFC 6455), so both sides are aware that the WebSocket termination is only a transient event, and that they can expect to immediately re-establish a connection again on retry.

We're working on additional refinements to the release process to minimize disruptions.

(I work at CloudFlare.)

Re:Universal SSL on Monday September 29, 2014 @10:33AM (#8382989)
Working on that. Lots and lots of certs to issue. Seeing about making message "smarter" (checking your individual status) if possible.
Glad to see Page Rule helped. Some revision on cache-control headers would help further.
Yes, I work at CloudFlare.
Just reached out via email to the site owner with some info/tips. We want to help.

CloudFlare doesn't cache HTML by default, though you can enable that with Page Rules. http://blog.cloudflare.com/introducing-pagerules-advanced-ca...

And the origin needs to be responding long enough for us to keep a copy in cache, once the Page Rule is enabled.