Finally, solved by copying the code above to my php script.

Thank you very much.

What a day (in a developer life).

FF2 IE Safari and Chrome all respect the expiration date, but FF3 seems to need to be told explicity to recheck.

Thanks for the comment – I should have mentioned this technique as it can also be very effective. It does have the benefit of being easier than trying to debug caching behaviour, where what you see can be deceiving. I have even noticed that some of the JavaScript libraries have built in support for adding a timestamp parameter to Ajax requests.

> This looks bad. Very very bad, if you check RFC 2616. Try not abusing
> no-store and must-revalidate, because they have specific, important
> meaning and throwing them around puts pressure on browsers and
> proxies to ignore them (internet on the grand scale really needs
> cacheable things).

Standards are a wonderful thing, but unfortunately we live in the Real World, where I need to make software that works in existing browsers. I can’t seriously be told that I am putting pressure on anyone by doing this. Yes, “the internet … needs cacheable things” – but perhaps I know my own application and know when caching is actually the wrong behaviour?

> You don’t seem to be expert on the subject, judging by the fact that
> you’ve seriously tried to use element for cache control.

I am no expert, nor did I claim to be. However I do have some practical experience of what works and what doesn’t, and so far this is the best solution I have found.

> Cache-control: max-age=5 (it’s freshness time in seconds) sent by the
> server, and nothing sent by the client should do the trick.

This won’t “do the trick” for at least two reasons:

1) As stated in my previous post, which I linked to, going back is also an issue, and AFAIK to solve it you must prevent the page from getting into the cache. Funnily enough, this is because of how the standards define the behaviour of the back button.
2) 5 seconds is a complete fudge, as would be 1 second (even though less risky in practice). The updates to these panels happen because something has changed, loading them from the cache is never the correct behaviour.

Did you even try to understand the use case I am talking about? Have you *tried* it in real life? Criticism is fine, but not when it is unecessarily agressive and plain wrong for the case I have discussed.

You don’t seem to be expert on the subject, judging by the fact that you’ve seriously tried to use element for cache control.

Cache-control: max-age=5 (it’s freshness time in seconds) sent by the server, and nothing sent by the client should do the trick.