Use this HTTP Header Viewer as a compact reference for common request headers, common response headers, and a selected list of HTTP status codes. It is useful for developers learning request and response vocabulary, QA reviewers checking terminology, and students understanding how web clients and servers communicate. Despite a broad tool name, the current component does not accept a URL or make a network request to inspect live headers. It displays predefined descriptions and a status-code lookup, so treat it as an educational reference rather than a remote header scanner.
The interface has three tabs: “Request Headers,” “Response Headers,” and “Status Codes.” Choose Request Headers to see examples such as Accept, Content-Type, User-Agent, and Cache-Control with accompanying descriptions. Choose Response Headers to inspect reference entries such as Content-Type, Cache-Control, X-Frame-Options, and Referrer-Policy. On the Status Codes tab, type a numeric code into the field; the page looks it up as you type and shows a description when one exists. A “All Status Codes” output lists the codes included in the helper.
The lists come from fixed objects in the HTTP tools utility. Request examples include Accept, Accept-Encoding, Accept-Language, Cache-Control, Connection, Content-Type, and User-Agent. Response examples cover content type and encoding, caching, several browser security headers, and referrer policy. The status list includes selected informational, success, redirect, client-error, and server-error codes—not every value defined by HTTP. If you type a code that is not in this object, the page displays “Unknown status code.” It does not expose response values from any particular server.
A realistic use is learning what a header name generally communicates before inspecting a request in browser developer tools or an API client. For instance, Content-Type describes the media type associated with a message body, while Accept communicates acceptable response types. Their actual values and effects depend on the protocol, application, and server configuration. The reference gives sample descriptions rather than recommendations for every deployment; do not copy a static security-header example into production without checking whether its policy suits the application.
To inspect a live site, use a browser network panel, command-line client, or approved observability tool that actually sends a request and reports the response. The URL Parser can decompose an address but also does not fetch it. For a cURL request that you already have, the cURL to Code tool can translate a limited subset into example client code. These distinctions prevent a common mistake: reading a generic header reference as if it were a measurement of a specific server's configuration or current response.
The component only changes local tab and input state and reads the static header/status objects; it does not contain a fetch for a target URL. This is a description of the current implementation rather than an overall site privacy or security statement. Avoid relying on sample status data as authoritative for every extension code or future standard update. Check a current protocol reference for compliance work, and verify real application behavior with a request capture and tests.
The header descriptions are useful starting points, but the same field can behave differently depending on request method, intermediary, cache state, and application policy. For example, a cache directive is interpreted in the context of a request or response and other caching controls; a static description cannot decide whether a particular value is correct. Pair the reference with the actual message captured from the client and server, and consult current specifications when implementing protocol behavior.
The status lookup converts the typed value to an integer before searching the included map. It is not a full response parser and does not show reason phrases received from a real origin. Codes not listed return the unknown fallback, which is not an indication that the code is invalid under every extension or future standard. For operational incident response, use logs, tracing, or a request tool that records status, headers, timing, and redirect history.
When learning headers, separate request-side negotiation and metadata from response-side representation and policy. A User-Agent example in the request list is only a sample string, not a parsed value from your browser. The User Agent Parser handles a supplied string separately, while this page's request tab remains a static catalogue. Keeping those roles distinct helps avoid drawing conclusions about a live connection from illustrative content.