HTTP Conditional Request Workbench

How to use HTTP Conditional Request Workbench

Evaluate supplied ETags and modification dates in the HTTP precondition precedence order. Follow strong If-Match checks before date checks, then weak If-None-Match checks before If-Modified-Since. Missing current ETags produce an unresolved result when a tag comparison needs them.

1. Provide current etag, current last-modified, if-match (optional), if-unmodified-since (optional), if-none-match (optional), if-modified-since (optional).
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• ASCII entity tags only, up to 100 tags per condition and 10 KB per list. Backslashes in ETags remain literal bytes, not quoted-string escapes.
• The date profile is IMF-fixdate, years 1601–9999, correct weekday, no leap seconds. Unsupported request date syntax is ignored and reported; unsupported current metadata is refused.
• This origin-server model assumes ordinary request checks succeeded. It does not model If-Range, cache recipients, extension methods or an already-succeeded state-changing request exception. Proceed does not mean HTTP 200 or application success.
• Inputs are processed on this device and are not automatically saved or uploaded.