Tiles cached if source cannot be found?

dlcs / protagonist

MIT License

7 stars 2 forks source link

Tiles cached if source cannot be found? #885

Closed donaldgray closed 3 months ago

donaldgray commented 4 months ago

Reported by Wellcome (so, at time of reporting, Cantaloupe 5.0.5, kdu 8.4.1).

The lustre volume for Cantaloupe was reaching capacity so some jp2's couldn't be orchestrated. This resulted in 404's being returned from Cantaloupe. After disk space was cleared up the issue went away, however user is still seeing blurry tiles cached in browser. Switching to an anonymous browser resolved issue so it looks like issue was browser related.

Check:

Are cache headers set for these 404 responses? If so, from where? Are they private or public?
Are they cached anywhere else?

griffri commented 3 months ago

I removed a newly orchestrated image from an Orchestrator volume and attempted to retrieve a tile in an anonymous browser - this resulted in a 404 with Cache-Control: public... and X-Cache: HIT headers set.

Cache-Control is also showing a max age of 2419200 - 28 days. This shouldn't be that high as Varnish is likely only going to cache it for about 30 seconds or so.

Are they cached anywhere else?

Outside of Varnish and in some cases CloudFront, they don't seem to be cached elsewhere.