Compare two sets of HTTP headers to find what differs between a working and a failing request, ignoring name case and order because neither is a difference.
Waiting for two header blocks
Paste one on each side. Case and order are ignored, because neither is a difference.
Waiting for both sides
Paste a header block on each side.
HTTP Header Comparison runs entirely on your device — nothing is uploaded, logged or stored.
You’re on the Free plan. Compare plans
The question is nearly always "why does this work here and not there", and the answer is nearly always one header — a missing Authorization, a different Accept, a Content-Type one side sends and the other does not.
Header names are case-insensitive, so `content-type` and `Content-Type` are the same header. They are reported as matching, with a note, rather than as a difference. A plain text diff treats them as different and buries the real finding under noise, which is why this is not a text diff.
Order is not a difference either, for the same reason: headers are a set rather than a sequence. Two captures of the same request made by different clients list them in different orders and are identical.
What is left after removing that noise is usually three or four rows, and one of them is the answer. Each side is labelled so the table reads as "working" against "failing" rather than "left" against "right".
A repeated header is folded the way HTTP folds it — joined with commas — except for Set-Cookie, which may never be joined and is shown as separate values.
Because HTTP header names are case-insensitive, so the two are the same header. Reporting it as a difference would be wrong, and it would bury the one row that matters under rows that do not.
Not for correctness — headers are a set. Order can matter for fingerprinting, where the sequence a client sends identifies it, but it never changes how a request is processed.
Folded with commas, which is how HTTP defines it. Set-Cookie is the exception: it may never be joined, so repeated Set-Cookie headers are kept separate.
Yes. A request line or a status line on the first line is recognised and shown separately rather than treated as a header.
No. Both blocks are parsed in your browser, which matters when they carry an Authorization header or a session cookie.