I checked the headers. This answer is cached.
age: 72
cache-control: max-age=600
x-cache: HIT
x-cache-hits: 2
this post was submitted on 27 Feb 2025
56 points (100.0% liked)
Programmer Humor
21353 readers
786 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
I once had a problem that wasn't caused by chaching.
It was caused by cache invalidation.
There are two hard problems in computing, naming things, cache invalidation, and off by one errors.
I once had a problem that wasn’t caused by caching. It was caused by Accounts Payable forgetting to pay the internet bill, and the ISP cutting our service halfway through a network test. So the beginning of the test cached that the network had internet access, but then the end of the- wait fuck it was caused by caching
I can't be the only one who has wasted half an hour wondering why something wasn't working before realising the response was cached.
Only a half hour? Amateur.
As long as you aren't blaming "the network" or "the firewall" without cause.
Usually I do my best to blame the network with cause!
Just because your bowser is not caching does not mean something else between you and the server is not caching as well.
thought it was obvious, but clearly /s
nah, it's dns.