The image didn’t show but when I did a ctrl+f5 on my end it restarted the connection and got updated headers. There may be a header caching problem going on somewhere, but that’s a bit harder to track.
Looks like I found something: conflicting CSP policies!
I’ve gone and removed Discourse’s inbuilt Content-Security-Policy rules and handed that over to the ones we’re rolling ourselves.
This SHOULD fix the issues going forward. Simply close your browser and attempt to reopen on pages where they don’t work and see if the images work now.
I did so, the image still doesn’t show on the example link above.
But, curiously, all the images are showing in this thread. (Edit, not now.)
Pressing CTRL + F5 makes the image show in the example link.
So, maybe it’ll fix it in threads from here on out, but previous threads are still impacted? I don’t know - I did close and open the browser.
You know, lemme check something.
It shows just fine in Vivaldi and in Firefox. Not in Chrome or Chromium. They may have something in the cache, even though I restarted. I’ll clear cache and take a peak.
Worst case, the CTRL + F5 works for now, as do at least two other browsers. I have no extensions that should be causing it - nothing is blocked in uBlock, I even turned it off completely and checked.
That’s a caching problem, nuke your browser cache and keep going. I had the same problem due to ‘page caching’ headaches, and because there wasn’t any page content updates it didn’t pull a new header.
Short story, purge your cache and it should resolve it going forward.
Purging my cache didn’t help. Weirdly, it now works fine in incognito mode. I purged all my cache, everything, and even rebooted. I suspect Chromium is giving me the issues.
It now works fine in other browsers. So, there’s that. When I’d previously checked, it did not.
I tried Chromium with no ad blocking and no VPN. I deleted all the cache and rebooted.
So, I’m going to mark this as solved - as it works fine in other browsers and it previously didn’t. I’d checked that before asking. Chromium will eventually get it sorted out. It works just fine in incognito mode, so maybe it’s not removing the cache entirely. That’s not a Lubuntu problem, nor a Discourse problem.