Compare two saved requests against a response's Vary fields
Admin ·
The same target can return different representations for different request fields. Use the recorded response to identify which fields the server declared in Vary, then compare the two captured request field sets.
Compare the catalog request fields
Load the example and select Compare Vary fields. The first block is a 103 Early Hints response. The checker uses the final HTTP 200 block, where two Vary lines name Accept-Language, Accept-Encoding and X-Workshop-Edition.
The encoding field has one matching line in both requests. The language field has one line in each request, with en in A and fr in B. The edition field has zero occurrences in A and one empty occurrence in B, so its values differ as recorded.
RFC 9110 Vary field semanticsRFC 9111 selection with the Vary field
Compare missing and empty fields
Remove X-Workshop-Edition from Request B and compare again. The row now reads Absent in both. Request A still has no field with that name, so the empty-versus-missing difference is gone.
Change the response to Vary: * and compare. The wildcard prevents matching under the cache rule, even if both requests contain the same fields.
Retain the evidence for a cache review
Restore the example and download the JSON report. The report records the response block, HTTP status, compared field names and occurrence counts. The captured values stay in the input panel.
Recorded equality is a starting point. A cache can combine lines when the field allows it or use normalization specific to a field's semantics. It also needs to consider freshness and other reuse conditions.
RFC 9111 selection with the Vary fieldRFC 9110 Vary field semantics
Common questions
Why compare requests for the same target and method?
This comparison assumes the primary cache lookup context is already the same. Vary describes additional request fields that can distinguish representations.
Do differently capitalized field names count twice?
Field names are case-insensitive. The checker compares the ordered field values under a single name and keeps the number of recorded occurrences.