I checked the headers. This answer is cached.
age: 72 cache-control: max-age=600 x-cache: HIT x-cache-hits: 2
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
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
nah, it’s dns.
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.
Now if only there’s one for off-by-one errors!
Believe it or not, still DNS
Usually I do my best to blame the network with cause!