HTTP response guides

Read status and repeated fields in an HTTP header dump

·

A header dump can include several HTTP blocks from a single navigation. Count the status lines before interpreting a field.

HTTP Header Checker

Separate early hints from the final response

For a capture beginning with HTTP/1.1 103 Early Hints followed by HTTP/2 200, block 1 is informational. Check block 2 for the final Content-Type. Two Cache-Control lines in that block stay in their recorded order.

IETF RFC 9110 — HTTP Semantics

Read a filtered report before sharing

A Set-Cookie line keeps its field name while its value is withheld. A Location value can still show the host and path. Verify that the visible names, paths and ordinary header values are appropriate for the recipient.

IETF RFC 9110 — HTTP Semantics

Keep values tied to the status that supplied them

If your capture includes informational responses followed by the final response, identify each status line before quoting a field. A hint from an early response and a caching directive from the final response answer different questions.

Compare the report with the original capture before sharing it. Filtered fields in a report do not remove private values from the original text file.

Common questions

Does a 200 establish what was on the page?

The status records the server response in the capture. This report reads headers and contains no response body.

What if the saved dump includes a message body?

Copy just the status lines and fields. A body after the header boundary is outside the supported input format.

Sources

Put it into practice.

Related guides