HTTP Headers Parser
Split header lines into names and values. No request is sent.
About this tool
Each line becomes a name and a value at the first colon. Leading space after the colon is not part of the name.
The page is a reader for text you already have. It does not open a connection.
How to use it
- Paste one header per line, with a colon between the name and the value.
- Parse the headers.
- Read the names and values. A line without a colon is reported.
Limitations
- The split is the first colon on the line. Later colons stay in the value.
- Nothing is requested. This does not check that a server would accept the headers.
Each line split on the first colon
Blank lines are skipped, and the first colon is the hinge
Each non-blank line is split on the first colon. The name is the text before that colon, trimmed. The value is the text after it, trimmed. Lines are kept in order, including two lines that share a name. The page does not join folded continuation lines. A line that continues a value with only a leading space, and no colon of its own, fails because a colon is required and it cannot sit at the start of the line. A line with no colon at all fails. The message says each header needs a name and a colon.
Names are not checked against a registry. A made-up name is accepted. A name with spaces is accepted after trimming, even if a real HTTP parser would reject it. The page does not send a request, does not add a host, and does not compute a content length. It reprints the pairs it could split. Empty values are allowed when the colon is present and the name is not empty, so a line that is only a name and a colon survives with a blank value.
What the trim changes
Space around the name and around the value is removed. Space inside the value, after the trim, stays. A line break that was a carriage return plus a line feed is normalized before the split, so a Windows paste and a Unix paste are read as lines. An HTTP request line such as a method and a path, with no colon, fails. Paste header lines, not the status line and not the body. If the body follows a blank line, the blank line is skipped and the body line will be parsed as a header and will fail when it has no colon.
Order is the record
Repeated names stay repeated. Cookies split across several lines stay several lines. Nothing here parses a cookie attribute or a cache-control directive into smaller pieces. If you need the request target, that is the URL parser, and it wants an absolute URL rather than a header block. Use this page to turn a header block into name and value lines you can read.
Privacy
Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.

