Cache Test Document

Expires [in 1 minute] Last-Modified [Last Night] about:document

This document has the following HTTP headers using RFC1123 date syntax (Date is always in RFC1123):

Date: Sat, 23 Aug 2025 05:46:20 GMT
Expires: Sat, 23 Aug 2025 05:47:20 GMT
Last-Modified: Sat, 23 Aug 2025 05:46:20 GMT

In local (Vancouver) time, the values are:

Date: Fri, 22 Aug 2025 22:46:20 PDT
Expires: Fri, 22 Aug 2025 22:47:20 PDT
Last-Modified: Fri, 22 Aug 2025 22:46:20 PDT

Your browser or proxy sent the following fields:

Pragma:
Connection: keep-alive
Proxy-Connection:
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
If-Modified-Since:
Request Method: GET
Remote Host:
Cache-Control: max-age=259200

In Netscape, you may check this using about:document. You may check the contents of your disk cache using about:cache. (Although clicking this link might not work, typing "about:cache" in Netscape's Open form should.)
In MSIE 3.0, you can check your cache in the Temporary Internet Files folder (assuming you're using drive C:).

If you Reload the document, you will notice that the Date (generated date) field updates. If you use the Back and Forward buttons (or click on the URL window and press Return) to navigate to the document, the Date field will be unchanged, unless your local cache size (in Netscape) is set to zero, or the Expires date has passed or is invalid (0). This is an indication that Netscape is getting the document from local cache.

A Reload causes Netscape to send a GET IF-Modified-Since with Pragma: no-cache to the server. This requests any proxy servers you are using to get a new copy of the document from this server, but only if it was modified since the copy in local cache was made. If you use Shift-Reload, the request is sent as an unconditional GET and the entire document is reloaded from this server.

More on Proxy Cacheing Servers
Back to Cache Tester Form
Get source of this script

Vancouver Webpages