Home/ Questions/Q 335893
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T10:11:29+00:00

It is a well known problem that IE caches too much of html, even

  • 0

It is a well known problem that IE caches too much of html, even when giving a Cache-Control: no-cache or Last-Modified header to everypage.

This behaiviour is really troubling when working with querystrings to get dynamic information, as IE considers it to be the same page (i.e.: http://example.com/?id=10) and serves the cached version.

I’ve solved it adding either a random number or a timestring to the querystring (as others have done) like this http://example.com/?id=10&t=2009-08-06_13:12:56 that I just ignore serverside.

Is there a better option? Is there another, cleaner way to acomplish this? I’m aware that POST isn’t cached, but it is semanticaly correct to use GET here.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    So, in the end, the only reliable way to do this (thanks to IE6) is using a
    random,
    or
    time bound
    querystring.

    You could use a
    time bound querystring
    that only changes every 15 seconds (or any other amount of time), so you’d lower the server hit count, as you’d see locally cached content for those 15 seconds.

    If you have
    a
    standard
    compliant
    browser, you can get away with only using
    ETags.

    • 0