HEADER

Bug now fixed

When Internet Explorer accesses a site it keeps a copy of the site on the local computer (caching). Unfortunately Internet Explorer will keep using this copy instead of checking if a later copy is available.

Most of the implementations also realize HTTP caching. Internet Explorer and Firefox do, but there is a difference in how and when the cached data is revalidated. Firefox revalidates the cached response every time the page is refreshed, issuing an "If-Modified-Since" header with value set to the value of the "Last-Modified" header of the cached response.

Internet Explorer does so only if the cached response is expired (i.e., after the date of received "Expires" header).

This raises some issues, and it is widely believed that a bug exists in Internet Explorer, and the cached response is never refreshed. I have now added some code which should force a refresh.

In general I have found that if there is a problem it is due to an Internet Explorer bug . For those of you who don't use it I highly recommend Firefox instead.

Cheers

Brett