PRACTICAL GUIDE

Read HTTP Headers Without Combining the Wrong Fields

Read pasted HTTP headers as ordered fields and grouped names while retaining repeated values.

Copy only the header block

Paste the field lines from your network inspector or a saved response. An optional first status or request line is supported. Do not include a response body, browser UI labels or a series of separate response blocks in the same input.

Compare names case-insensitively

HTTP field names are case-insensitive. The ordered view retains their original spelling, while the grouped view uses lowercase names. This makes it easier to spot repeated entries without pretending that differently capitalized names are separate fields.

Keep repeated values separate

Some fields can be combined under specific rules, but others cannot safely be joined with a comma. Set-Cookie is a familiar example. This parser retains every occurrence so you can inspect the original values before applying field-specific interpretation.

Interpret policy with the right context

A parsed header is not a security verdict. Caching, cross-origin behavior and cookie settings depend on the complete response and browser context. The tool does not contact a server, follow redirects, validate a certificate or test whether a policy is effective.

Put it into practice