Revenir au blog

Suivre et s’abonner

Ingénierie

Page 3 sur 3

Log4Shell exploit found in Log4j | FastlyÉquipe de recherche en sécurité Fastly, Xavier Stevens, +1
CVE-2021-44228 is a Remote Code Execution vulnerability in the Apache Log4j library being actively exploited. We provide our observations into the exploit and a summary of its impact.
SécuritéIngénierie
30 Years of Web: Building for TomorrowLee Chen
The web’s infrastructure — and the applications we build on it — must constantly evolve to meet the ever-transforming expectations of modern and future end users. We’ve gathered five lessons today’s builders can use to drive the next three decades of the web.
Informations sur le secteurIngénierie+1
Grinch bots penalized w/ enriched security data & our edge cloud platform Brooks Cunningham, Architectes de solutions d'entreprise Fastly
In this post, we’ll show how you can use information from an origin response to add an abuse IP address to our penalty box. We've been touting the promise of security at the edge, and this is just one example of what it can do.
SécuritéIngénierie+1
30 Years of Web: Future-Ready AppsJana Iyengar
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, and scalable user experiences. We must embrace a more dynamic mindset in how we approach web development and consider the tools we need to get there.
Informations sur le secteurIngénierie+2
30 Years of Web: Future DemandsDavin Camara
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 builders in general — can champion innovation, mainly around architecture and security.
Informations sur le secteurIngénierie+4
You can now test Compute code in Fastly FiddleAndrew Betts
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 language that compiles to WebAssembly, and now you can write Compute code in Fiddle too.
IngénierieProduit+2
Get started with Fastly logging and Compute@Edge | FastlyAlex Kesler
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 logs in your application, and confirming the delivery of those logs to your target logging destination.
IngénierieWebAssembly+1
Preventing SSRF: Apache CVE-2021-40438 | FastlyÉquipe de recherche en sécurité Fastly
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 a new templated rule to prevent exploitation.
IngénierieSécurité
Compute: The JavaScript Support you Demanded | FastlySean Leach
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 serverless build environment.
ProduitIngénierie+1
How to configure your Fastly services with TerraformMark McDonnell
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 a step back and look holistically at how to configure, manage, and deploy Fastly services using Terraform.
IngénierieProduit+1
How to test site speed optimizations with ComputeLeon Brocard
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 between the original and transformed page versions.
IngénierieCompute
Minimizing ossification risk is everyone’s responsibility Mark Nottingham
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 needs to be possible to introduce changes gradually, without harming communication where only one party understands the change — and this is everyone’s responsibility.
IngénierieInformations sur le secteur
Meilleures pratiques pour les implémentations multi-CDN | FastlyDima Kumets
Découvrez le fonctionnement des multi-CDN et les avantages de cette approche. Découvrez comment mettre en œuvre une architecture multi-CDN en suivant ces 8 étapes.
Réseau de périphérieCDN et distribution+1