Information and status of [not] stored objects
Format:
Timestamp Tag Code Date LM Expire Content Expect/Length Methode Keywith:
Timestamp | The time this entry was logged. (millisecond resolution since 00:00:00 UTC, January 1, 1970) |
Tag | SWAPIN (swapped into memory from disk), SWAPOUT (saved to disk) or RELEASE (removed from cache) |
Code | The HTTP reply code when available. For ICP requests this is always "0". If the reply code was not given, it will be logged as "555." |
| The following three fields are timestamps parsed from the HTTP reply headers. All are expressed in Unix time (i.e.(seconds since 00:00:00 UTC, January 1, 1970). A missing header is represented with -2 and an unparsable header is represented as -1. | |
Date | Time from the HTTP Date reply header. If the Date header is missing or invalid, the time of the request is used instead. |
LM | The value of the HTTP Last-Modified: reply header. |
Expires | The value of the HTTP Expires: reply header. |
Content | The HTTP Content-Type reply header. |
Expect | The value of the HTTP Content-Length reply header. Zero if Content-Length was missing. |
/Length | The number of bytes of content actually read. If the Expect is non-zero, and not equal to the Length, the object will be released from the cache. |
Method | The request method (GET, POST, etc). |
Key | The cache key. Often this is simply the URL. Cache
objects which never become public will have cache keys that include a
unique integer sequence number, the request method, and then the URL. ( /[post|put|head|connect]/URI ) |