Read HTTP status codes in order across a recorded exchange
Admin ·
A single browser or proxy capture can show several HTTP responses. Read the status line and its own fields before deciding whether the server accepted the request, redirected it or returned an error.
Compare 304, 307 and 308 in the 3xx class
Choose 3xx Redirection and clear the search field. Nine codes appear in this class. Open 304, 307 and 308. A 304 validates a cached response, while 307 and 308 describe temporary and permanent redirects that preserve the request method on automatic redirection.
Open the specification for a code to check its exact behavior. The reference names the IANA snapshot dated 2025-09-15. Search 104 under All to read the temporary registration's listed expiry of 2026-11-13. For a current registration, follow the IANA link.
IANA HTTP Status Code RegistryRFC 9110, status codesRFC 9110, 307 Temporary Redirect
Follow three recorded response blocks
In the reference, expand Check a saved response. Choose Load capture example, then Inspect capture. The table shows three blocks in capture order. Read each status with the fields in its row.
The 103 is an early hint. The 307 directs the client to another location, while preserving its method on automatic redirection. The 200 belongs to the last recorded block. Use the redirect chain checker if you also have the starting URL and need to resolve relative locations.
| Block | Expected status | Evidence in its header fields |
|---|---|---|
| 1 | 103 Early Hints | The Link field exists. Its value is withheld in the report. |
| 2 | 307 Temporary Redirect | Location points to /next with the query withheld. Set-Cookie is present and its value is withheld. |
| 3 | 200 OK | Content-Type is application/json. |
Choose the next check for a client error
For 401, review the server's authentication challenge and check whether the request supplied suitable credentials. For 403, check the resource and the server's policy. Repeating the original credentials alone may leave the refusal unchanged.
Search for rate limit and open 429. A Retry-After field can supply a delay in seconds or an HTTP date. Consider the operation's retry semantics and the client policy before scheduling another attempt. If the field is absent, use the service's documented rate-limit behavior.
RFC 9110, HTTP authenticationRFC 6585, 429 Too Many Requests
Keep the recorded number when a code is unknown
Search 599. You should see that the local registry has no dedicated entry and that the number belongs to the 5xx class. RFC 9110 describes handling an unrecognized 5xx status as 500. The exact value remains useful when comparing a log with a provider's documentation.
Download the capture report to preserve the block numbers and displayed fields. Compare each row with your original capture before sharing. Keep the original source private if it includes cookies, credentials or sensitive URLs.
Common questions
Does a temporary registration stay in the dated reference?
The reference preserves the entries from its snapshot and displays the listed expiry for 104. IANA publishes any subsequent registration changes.
Is 103 the final response?
103 is informational. It can precede the final response. A capture ending at 103 gives you the hint headers and leaves the final status unknown.
Why can 304 appear without a Location header?
304 validates a cached representation for a conditional GET or HEAD. The client can reuse its cached copy. The 3xx class includes several behaviors besides following a new URL.
Sources
Put it into practice.
Related guides
- Read a saved HTTP response header dump
- Read recorded redirect hops
- HTTP Method Safety and Retry Guide
- Compare a File Extension With Its Header
- Compare Private and Shared Cache Freshness
- Read a Saved Link Header for Pagination
- Resolve a URI and Check its IANA Scheme
- Preview a Buffered API Response
- Trace HSTS Preload and Saved Header Evidence
- Compare Saved Redirect Chains
- Explain a Stylesheet Blocked by nosniff