Caching

Capability tests probe optional HTTP features that servers may or may not implement. Unlike compliance tests, these are unscored — they map what each server supports rather than what it fails at.

Scoring

All capability tests are unscored:

Pass — Server correctly supports the feature
Warn — Server does not support the feature (not a failure)
Fail — Only for actual errors (unexpected status codes, connection errors)

Conditional Requests (Caching)

These tests check whether the server supports ETag and Last-Modified based conditional requests (RFC 9110 §13).

ETAG-304

ETag conditional GET returns 304 Not Modified.

LAST-MODIFIED-304

Last-Modified conditional GET returns 304 Not Modified.

ETAG-IN-304

304 response includes ETag header.

INM-PRECEDENCE

If-None-Match takes precedence over If-Modified-Since.

INM-WILDCARD

If-None-Match: * on existing resource returns 304.

Conditional Request Edge Cases

These tests probe how servers handle invalid or unusual conditional headers — future dates, garbage values, unquoted ETags, and weak comparison (RFC 9110 §13).

IMS-FUTURE

If-Modified-Since with future date ignored.

IMS-INVALID

If-Modified-Since with garbage date ignored.

INM-UNQUOTED

If-None-Match with unquoted ETag.

ETAG-WEAK

Weak ETag comparison for GET.