Read status and repeated fields in an HTTP header dump
Admin ·
A header dump can include several HTTP blocks from a single navigation. Count the status lines before interpreting a field.
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.
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.
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
- Read recorded redirect hops
- Compare recorded response headers
- Interpret a security header grade
- How to Read a Recorded HTTP Status Sequence
- HTTP Method Safety and Retry Guide
- Read a saved domain registration record
- Check and Fix Open Graph Tags in HTML
- Find the robots.txt Rule That Controls a URL
- How to Read a Reduced User-Agent String
- Compare a File Extension With Its Header
- Test Apache Page and Folder Redirects
- Test a CSP in Report-Only and Enforce Modes
- Build a Reusable cURL Request
- Check a cURL-to-Fetch Translation
- Compare Private and Shared Cache Freshness
- Read a Saved Link Header for Pagination
- Check Recorded Browser Feature Allowlists
- Check CORS on a Saved Catalog Response
- Review Scope in Saved Cookie Headers
- Compare Requests Against a Vary Header
- Preview a Buffered API Response
- Compare Requested and Granted OAuth Scopes
- Read Saved Font Loading Evidence
- Set Browser and CDN Freshness
- Review CDN Hits Beside Cache Lifetimes
- Check Version Details in Saved Server Headers
- Explain a Stylesheet Blocked by nosniff