Comment 4 for bug 2039251

Sorry, I made a mistake in my previous comment - there was in fact a caching layer present before my recent frontend changes. The structure of the configuration is fairly different because we're now having the `squid-reverseproxy` charm do a lot more of the heavy lifting, but I've just gone through it all and can't find any relevant differences. Still digging.