Network · Made a little simpler

Vary Header Checker

Select a response block and compare the fields named by Vary across two saved request header sets. See presence, repetition, exact recorded matches and wildcard behavior.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Compare two captures for the same request target and method. Leave a request box empty only if its captured field set is empty.

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

Vary Header Checker: how to use it

  1. Paste the recorded response header lines or import a response capture. Select a block if the response you need is earlier in the capture.
  2. Paste the header fields from two requests for the same method and target, one named header per line.
  3. Compare the listed fields and review missing and repeated values. Copy or download the JSON report with field names, counts and outcomes.

Limits and notes

Up to 50,000 characters per input, 300 fields per selected block or request, and 100 distinct Vary members. The comparison preserves field-line order and trims surrounding whitespace. Field-specific semantic normalization, cache freshness and reuse eligibility are outside this comparison.

How your privacy works →

Vary Header Checker: common questions

What does Vary: * do?

It prevents a stored response from matching another request under the Vary comparison in RFC 9111.

Does a missing request field match a present but empty field?

A missing field matches only missing in the other capture. The report distinguishes a present line with an empty value from zero recorded lines.

Which response block is used?

By default the checker selects the last final response. Enter a block number to check another final response in the recorded trace.

Guides