No Validator, No Expiration Test
Failed
The HTTP 1.1 specification allows pages with no validator or expiration to be be cached, but does not expect them to be cached.
Because the two browsers with the vast majority of market share (Internet Explorer and Netscape) will not cache this type of page, many dynamic web applications rely on this behavior.
From section 13.4 of the HTTP 1.1 specification:
If there is neither a cache validator nor an explicit expiration time associated with a response, we do not expect it to be cached, but certain caches MAY violate this expectation (for example, when little or no network connectivity is available).