User reported an image-related issue with ProCache

[Michael Lenaghan]

A user reported an image-related issue with ProCache: when they set the focus of an image, they still get the image as it looked before they set the focus.

The cache-related HTTP headers for the image look roughly like this:

Cache-Control: max-age=31536000
Date: Tue, 10 Jun 2025 14:38:03 GMT
Expires: Wed, 10 Jun 2026 14:38:03 GMT
Last-Modified: Tue, 10 Jun 2025 14:28:17 GMT

That explains the issue: images are cached for a year, with no freshness check.

What I would have expected is one of two things:

• Additional `Cache-Control` values like `must-revalidate` that force freshness checks; or
• A uniquely generated image name each time the image is modified in any way.

I can make one of those happen, but before I do: am I misunderstanding something about how ProCache is meant to be configured and used?

[elabx]

 

1 hour ago, Michael Lenaghan said:

• A uniquely generated image name each time the image is modified in any way.

You can do this with the $buster API

[JamesFletcher]

On 6/10/2025 at 10:13 PM, elabx said:

Spoiler

Image-related issues can disrupt site performance and user trust. This mirrors the online casino space, where user experience is crucial. Platforms like https://gamblingorb-it.com/casino-online/ emphasize usability and speed, offering insights into how streamlined design and technical optimization greatly impact reliability, whether you're managing content or playing online games.

You can do this with the $buster API

Thanks for the link.

Edited 9 hours ago by JamesFletcher

[Michael Lenaghan]

Thank you, @elabx. I changed my image urls from `$img->url` to `$img->URL`, and they now work as expected.