The Forgotten Power of the HTTP Cache
ETags, Vary, and the headers your CDN is already willing to respect if you would only bother to set them.
This is placeholder body copy. In a real post there would be an argument here, built one paragraph at a time, with the kind of small detours that make a technical essay feel like it was written by an actual human.
The repository this page lives in exists to demonstrate behavior of the Next.js router, so the content is intentionally boring. Any similarity to real insight is entirely coincidental, if occasionally welcome.
If you are reading this from a prefetch-triggered hover, congratulations, the link worked. If you are reading it after a full navigation, that also counts, and you have learned something about how caches behave under load.
More posts
Writing Fast Tests Without Cutting Corners
Test design choices that keep a suite under thirty seconds even as the product grows past a million users.
The Case for Boring Stacks
Why the most interesting work at most companies is built on the least interesting technology choices.
The Hidden Cost of Client Components in Next.js
A look at how 'use client' drags entire dependency trees across the network boundary, and how to audit the damage.