Review a Saved Conditional HTTP Request

Read a saved request and evaluate its preconditions against supplied representation state,keeping the source,exact inputs and both complete native reports.

• Choose a saved UTF-8 HTTP/1.1 request up to64KiB with original CRLF headers/exact Content-Length. Actual GET/HEAD/PUT/POST/DELETE/PATCH method is read from source. Supply representation exists,one current quoted entity tag and optional zoned last-modified time;these are not fetched. Original strong If-Match,weak If-None-Match,wildcard/date precedence and304/412 decisions apply. Repeated tag fields combine in order;duplicate date fields,Range/unsupported if-* fields or malformed values retain the whole parsing checkpoint. All conditions validate even when precedence ignores them. Proceed leaves normal status undecided. This checks preconditions for an otherwise eligible request;no full server eligibility,authorization,range,network or state verification. The ZIP retains complete raw headers/body/private credentials,parser report,exact arguments and native report unredacted. Original30second workers remain.
• Exact B28 original64KiB/65536unit/safe255unit1020byte File[] parser/3member checkpoint and file-only presenter reused unchanged. Fixed original GET response context is irrelevant to actual request methods. No old package processing replay.
• One original precondition worker with30s/4MiB JSON/100tag and65536character per conditional budgets unchanged. New90sconnection/8MiBZIP/4MiBentry/6finalmembers. All original reports and exact string arguments independently checked.
• If-Match/If-None-Match duplicate lines combine in original order;date fields at most one. Range/unsupported if-* names refuse. No conditional headers is a valid proceed/statusnull result. Unknown representation tag/time may skip relevant checks according to original rules;these are explicit supplied-state limitations.