User:Sennheiser/cache

The color of the list dot indicates the cacheability of the resource. The following server's clock appears to be inaccurate. This can cause difficulties in caching its content. Please ask the administrator to synchronise its clock (this may also be caused by a proxy between you and the Web server).

   * en.wikipedia.org - 59 min 38 sec behind

   *
     http://en.wikipedia.org/wiki/Wikipedia:Village_pump
     Date   	Tue, 03 Feb 2004 15:34:03 GMT
     Expires   	  -
     Cache-Control   	s-maxage=0, private, must-revalidate, max-age=0
     Last-Modified   	13 min 47 sec ago  (Tue, 3 Feb 2004 15:20:16 GMT) validated
     ETag   	  -
     Content-Length  	  - (actual size: 84420)
     Server  	Apache/1.3.29 (Unix) PHP/4.3.4

     This object has been deliberately marked stale. It can be validated with Last-Modified. It won't be cached by proxies, because it has a Cache-Control: private header. Because of the must-revalidate header, all caches will strictly adhere to any freshness information you set. It doesn't have a Content-Length header present, so it can't be used in a HTTP/1.0 persistent connection. The clock on this Web server appears to be set incorrectly; this can cause problems when calculating freshness.
     Images
         o
           
           Date   	Tue, 03 Feb 2004 15:34:11 GMT
           Expires   	  -
           Cache-Control   	  -
           Last-Modified   	23 weeks 1 day ago  (Mon, 25 Aug 2003 04:20:40 GMT) validated
           ETag   	"440d9-67b9-3f498e98"
           Content-Length  	25.9K (26553)
           Server  	Apache/1.3.29 (Unix) PHP/4.3.4

           This object doesn't have any explicit freshness information set, so a cache may use Last-Modified to determine how fresh it is with an adaptive TTL (at this time, it could be, depending on the adaptive percent used, considered fresh for: 4 weeks 4 days (20%), 11 weeks 4 days (50%), 23 weeks 1 day (100%)). It can be validated with Last-Modified. The clock on this Web server appears to be set incorrectly; this can cause problems when calculating freshness.
         o
           
           Date   	Tue, 03 Feb 2004 15:34:14 GMT
           Expires   	  -
           Cache-Control   	  -
           Last-Modified   	16 weeks 13 hr ago  (Tue, 14 Oct 2003 02:12:51 GMT) validated
           ETag   	"237b89-35fb-3f8b5ba3"
           Content-Length  	13.5K (13819)
           Server  	Apache/1.3.29 (Unix) PHP/4.3.4

           This object doesn't have any explicit freshness information set, so a cache may use Last-Modified to determine how fresh it is with an adaptive TTL (at this time, it could be, depending on the adaptive percent used, considered fresh for: 3 weeks 1 day (20%), 8 weeks 6 hr (50%), 16 weeks 13 hr (100%)). It can be validated with Last-Modified. The clock on this Web server appears to be set incorrectly; this can cause problems when calculating freshness.
     Objects
         o
           http://en.wikipedia.org/style/wikistandard.css
           Date   	Tue, 03 Feb 2004 15:34:28 GMT
           Expires   	  -
           Cache-Control   	  -
           Last-Modified   	4 days 17 hr ago  (Thu, 29 Jan 2004 22:17:23 GMT) validated
           ETag   	"207d1b-8f0-40198673"
           Content-Length  	2.2K (2288)
           Server  	Apache/1.3.29 (Unix) PHP/4.3.4

           This object doesn't have any explicit freshness information set, so a cache may use Last-Modified to determine how fresh it is with an adaptive TTL (at this time, it could be, depending on the adaptive percent used, considered fresh for: 22 hr 39 min (20%), 2 days 8 hr (50%), 4 days 17 hr (100%)). It can be validated with Last-Modified. The clock on this Web server appears to be set incorrectly; this can cause problems when calculating freshness.
         o
           http://en.wikipedia.org/style/wikibits.js
           Date   	Tue, 03 Feb 2004 15:35:16 GMT
           Expires   	  -
           Cache-Control   	  -
           Last-Modified   	4 days 17 hr ago  (Thu, 29 Jan 2004 22:17:23 GMT) validated
           ETag   	"207d19-14d2-40198673"
           Content-Length  	5.2K (5330)
           Server  	Apache/1.3.29 (Unix) PHP/4.3.4

           This object doesn't have any explicit freshness information set, so a cache may use Last-Modified to determine how fresh it is with an adaptive TTL (at this time, it could be, depending on the adaptive percent used, considered fresh for: 22 hr 39 min (20%), 2 days 8 hr (50%), 4 days 17 hr (100%)). It can be validated with Last-Modified. The clock on this Web server appears to be set incorrectly; this can cause problems when calculating freshness.