Many websites today are really applications, and we should be building them as such. To do that, we need application architectures and networks that are capable of supporting fast, secure…

As we look back to celebrate the 30th anniversary of the website, it’s also worth thinking about the next 30 years. There are a couple of areas where we — as engineers, developers, and…

Fastly customers have been using our Fiddle tool for years to try out ideas for edge logic in VCL. With the advent of Compute last year, we made our edge compute network accessible to any…

In this tutorial, we’ll walk you through the basic steps of outputting messages to STDIO and tailing that output with the Fastly CLI as well as configuring a log streaming endpoint, emitting…

Our Security Research Team provides guidance on how to address CVE-2021-40438, a vulnerability in Apache HTTP Server version 2.4.48 and earlier, by patching impacted version(s) and enabling…

Curl, or cURL, is a utility that’s shipped by default on operating systems like MacOS and many Linux distributions that allows you to send an HTTP request to a URL and receive the result. In…

With JavaScript now available for WebAssembly and Compute, you can get started faster than ever with a language you already know, while ensuring the speed and security you need in a…

As you start to build more at the edge, it becomes ever more important to deploy edge logic in the same way you deploy changes to your own applications and infrastructure. Today, we’ll take…

In this post, we show how to test site speed modifications before implementing them using Compute and WebPageTest, a web performance tool that uses real browsers, to compare web performance…

Building protocols in a way that anticipates future change in order to prevent ossification is critical. Because it’s impossible to upgrade everyone on the internet at the same time; it…

QUIC version 1 is officially formalized, and QUIC deployments will now move away from using temporary draft versions to the newly minted version 1.

Following the DRY principle isn’t just for engineers. It also cuts the time it takes to make updates in multiple places and reduces errors for our documentation team.