
Cache headers for images: immutable, hashed names and CDNs
A hashed image URL with immutable costs 0 requests on repeat. A no-cache image still costs a 162-byte 304. Node code and measured bytes.
Tag archive

A hashed image URL with immutable costs 0 requests on repeat. A no-cache image still costs a 162-byte 304. Node code and measured bytes.
A practical review of Sec-Fetch headers, endpoint policy, caching, and deployment limits.
How opaque responses, MIME handling, CORP, and CORS interact at a cross-origin media boundary.
Every shot on dribbble.com/shots is drawn from a URL like...
How to Schedule Recurring HTTP Data Cleanup Triggers Without Task Executors (and...
Two paths, one config file, different headers I run a small portal behind nginx on a...
An inherited set of URLs Imperial Seedlings Guide is a static site built with Astro 5 and...
The per-request email-protection key on our own host is one byte wide, so it repeats: one of our URLs returned byte-for-byte identical responses twice in 30 fetches, correcting our own 10 November claim.

HTTP headers explained in simple English: request vs response headers, Host, Cookie, Cache-Control and more, with a real example and DevTools tips today.
You restore the page, publish the redirect, purge nothing, and users keep seeing the error for hours. A walkthrough of every layer that can remember a broken response, and how to tell which one is doing it.
A cold load of one of our own app pages reaches four origins - and the served document names neither of the two we depend on.
Our API host sets exactly one cookie, on exactly one route. Here are its five attributes, its measured lifetime, and the route next to it that sets nothing.