Then either you didn't actually flush your browser cache completely, or there is another network cache involved. For example, your corporate or ISP caching proxy may be holding a copy of the page. AOL and Earthlink, for example, have all of their users behind such caching proxies in order to minimize out-of-network traffic (to minimize "bandwidth").

If you have not done so, check your HTTP server response headers using a server headers checker such as "Live HTTP Headers" and look at the Expires and Cache-Control headers sent by your server. You may want to configure your server to explicitly expire the pages a short time after they are fetched from your server, or you may want to allow only "private" (i.e. end-user) caching of your pages if the pages change frequently.

Another Cache-Control setting of interest is "must-revalidate". This allows pages to be cached in accordance with the public/private Cache-Control and Expires headers, but also tells the client to check with the server on every client page-view, sending an If-Modified-Since request header to the server. If the page has been modified since the client last cached it, the server responds with a 200-OK response and a new copy of the page; If not, it responds only with a 304-Not-Modified header.

Try a search for "caching tutorial for Web authors and webmasters" for more information.

Jim

For example, your corporate or ISP caching proxy may be holding a copy of the page