Firefox is showing an outdated JSON file while Chrome displays the latest version.

Quick check before anyone spends their time actually genuinely trying debug the requests: Now when you see the outbound link is nofollow, as a SEO enthusiast do you still have this issue, or are happy to close it now?

Thanks for the reply. The issue is genuine and not related to SEO. I included the page only so others could reproduce the problem. I'm looking for help understanding why Firefox sometimes displays outdated data while other browsers show the latest version. i frequently updating values of fruits items.

The api endpoint returns 403 so I'm not looking into that further; that's served by your wp plugin so assume they have figured out the correct headers and webcompat on their side.

Besides that you return an hash–like json that seems static, not generated — its hash changes with content, right? So if you have a change you generate a new file… or am misunderstanding it?

Which endpoint you're having trouble with?

Thanks jbr. The JSON file is regenerated whenever the data changes, so the filename stays the same but the content is updated. The endpoint I'm having trouble with is:

https://bloxvalues.net/wp-content/uploads/blox-fruits-stock/data.json

Firefox occasionally shows an older version while other browsers load the latest data.

OK the hashed files come from litespeed scripts; it's the caller, not the content.

The file you posted is 404.

Could you point where the app accesses the raw json file directly? Or it's not at all connected to the app functionality and you're just seeing cached content when you check it just yourself using the wp-content attachment? (If so, post the headers you get for it in your devtools network pane; and then make the same request in private window and note any differences, to inform client cache vs CDN cache impact.)

Because in the app I see it hits the REST endpoint like bloxvalues.net/wp-json/bloxcalc/v1/items which handles its etags, thus HTTP 304 modified statues etc. — and is not actually a JSON file, it's an JSON response on a WP API endpoint; that's further cached on your cloudflare edges.