When we launched Workers much of the focus was on use cases surrounding websites running on origins that needed extra oomph. With Workers you can easily take a site and introduce a raft of personalization capabilities around a range of services.
We deployed a Cloudflare worker in front of www.cloudflare.com and api.cloudflare.com, that has since served over million requests. Here's what we learned about debugging and "failing open" when writing workers.
On June 4, Cloudflare will be dropping support for TLS 1.0 and 1.1 on api.cloudflare.com. Additionally, the dashboard will be moved from www.cloudflare.com/a to dash.cloudflare.com and will require a browser that supports TLS 1.2 or higher.
To everyone in Cloudflare, account security is one of our most important tasks. We recognize that to every customer on our platform, we are critical infrastructure. We also know that the simplest attacks often lead to the most devastating of outcomes.
Back in May last year, one of my colleagues blogged about the introduction of our Python binding for the Cloudflare API and drew reference to our other bindings in Go and Node. Today we are complimenting this range by introducing a new official binding, this time in PHP. This binding