1. Upload an image as part of a post or comment
  2. Navigate to your profile page -> Uploads
  3. Open image in new tab (and save the URL)
  4. Press “delete” on the image
  5. Attempt to navigate to the saved URL

This should result in a 404 error. Currently, it shows the screenshot. Below is a screenshot I deleted from my profile:

screenshot of the lemmy create post page

Here is confirmation from my user profile taken after the above screenshot was deleted:

screenshot of the lemmy user profile page on "uploads" tab, showing the most recent upload 7 hours ago

  • taaz@biglemmowski.winEnglish
    6·
    4 days ago

    It could still be cached by your instance infra, in your case I see cloudflare headers and cache HIT so it might take a bit before the image goes away, depending on the settings of your instance.

    E: it’s also possible your instance does not have cache revalidation configured correctly and as such the image could be cached almost indefinitely (the headers currently say it can be cached for a maximum of a year). @Lodion@aussie.zone

    • Nothing4You@programming.devEnglish
      2·
      4 days ago

      this is most likely the case, pict-rs headers allow caching basically forever and don’t include revalidation. i’ll bring this up with the pict-rs dev about changing the default or adding a config option for this.

      something like s-maxage should do the job, though it’d probably be up to the instance operator to decide on a sane value for that, as it will always be a tradeoff.

      ideally, lemmy would have a mechanism for cache purging, but i suspect that this might be something that people will have to implement themselves using the 1.0 plugin system at some point, as it’s probably not going to become core functionality to support e.g. cloudflare cache purging.

      edit: it seems that the 1 year cache is already an override by aussie.zone - pict-rs only sets a 7 day max-age, which is passed on by lemmy as can be seen e.g. on lemmy.ml, which isn’t behind cloudflare, or on progamming.dev, which is behind cloudflare but doesn’t seem to be overriding it.

      • Lodion 🇦🇺@aussie.zone
        4·
        4 days ago

        Probably both this and cloudflare caching. Looks like I set CF to cache for 1 year at some point, I can lower it… but that won’t “fix” this, only limit the time its an issue for.