Check Cache Freshness in a Saved HTTP Response

Parse a saved response, then review explicit cache freshness from its headers and supplied clocks, keeping the source, exact inputs and both complete native reports.

• Choose an original UTF-8 HTTP/1.1 snapshot file up to64KiB. Preserve CRLF headers and exact Content-Length; use GET/HEAD context. Downstream review accepts200 responses only. Date is required; Date/Expires use strict IMF-fixdate, one Date/Age/Expires each. Repeated Cache-Control fields combine in order; absent Age=0. Supply request, response and observation clocks with seconds/zones and choose private/shared. Original max-age/s-maxage/Expires and no-cache/no-store/private rules calculate explicit age, freshness, revalidation and storage flags. Unsupported/conflicting directives or bad clocks retain the complete parsing checkpoint. No heuristic lifetime, stale allowance, status eligibility, Vary, Authorization, real cache-state or network observation. The ZIP keeps all original source headers/body/private values, parser report, exact calculator inputs and native report unredacted. Original30second workers remain;
• Own64KiB/65536unit input,safe255unit/1020byte filename;8MiBZIP/4MiBentry/3CP/6final members/90s connection. Both original30s workers and strict original parser/directive/ISO date limits unchanged. Consumer revalidates only the new actual source with original File[] processing,not old accepted packages.
• Header projection accepts strict IMF-fixdate1601..9999 with weekday/calendar roundtrip;does not infer Date or missing clocks. Repeated Date/Age/Expires refuse,Cache-Control combines in source order with exact original trimmed values. Missing Age0/cachecontrol empty/missing Expires original zero lifetime semantics.
• Complete native files and every ordered ZIP member independently compared in full;original UTF8 body byte lengths retained. Native original File[] parser and all-string cache worker separately required.