I’m in the UK, due to differences of opinion between Imgur owners and the UK government whenever i access a thread with an embedded imgur picture imgur sends the following picture

if i see this it usually reminds me to turn on my VPN, however connect seems to have cached this image so that even when, after i VPN to another location, i refresh it regurgitates the above instead of the actual picture (below)

I managed to work around this by going to Settings -> Cache Stats -> Scroll to the bottom -> Clear cache and then refreshing the page but clearing the entire cache every time someone comments with a picture while i don’t have my VPN on is a little onerous.

I imagine this affects all UK users of the app, along with anyone in any other jurisdiction that Imgur is blocking.

The response headers from imgur are noticeably different for actual pictures, vs the “not available in your region” picture. could this picture be exempted from being cached?

I managed to replicate the issue using PIA streaming optimized servers (other vpns will probably work too)

Steps to Recreate

Expected Behaviour

Blocked image should not have been cached, Non blocked image should be shown

Current Behaviour

Blocked image is cached, and thus shown

  • kuro@lemmy.caM
    3·
    4 days ago

    Hi, thank you for the report. I’ve added a new setting in v389 (if you are on the beta track it should be available now) for Image Domain Rewrites. If i.imgur.com isn’t working for you then you could try replacing it with an imgur mirror such as imgur.kageurufu.net. Potentially that might work for you? Cheers!

    Direct link if you’re in app: Settings: Image Domain Rewrites

    • PrettyFlyForAFatGuy@feddit.ukOP
      1·
      4 days ago

      Seems to work thanks, I do notice that the input fields for that setting were auto-capitalizing when i added both e.g. i.imgur.com became I.imgur.com, so didn’t work the first time round until i noticed that.

      Also when i went back to look at the picture again (having cleared the cache) i got an exception that looked like it was trying to pull the image from the cache and subsequently understandably failing although the try again button it showed did work perhaps it shouldn’t have been trying to get it from the cache after a cache clear