Description
Split HTTP comma lists with the existing quote/escape-aware scanner, not generic parentheses or CSS syntax; trims outer whitespace and preserves quoted text.
HTTP field names are case-insensitive, while values follow each field’s own grammar. Repeated occurrences sometimes form lists but cannot always be combined. Quoted values, optional spaces/tabs and quality weights need their own treatment; the tools here use explicit field records or a stated text subset.1
Split HTTP comma lists with the existing quote/escape-aware scanner, not generic parentheses or CSS syntax; trims outer whitespace and preserves quoted text.
When to use this tool
Use this tool to split HTTP comma lists with the existing quote/escape-aware scanner, not generic parentheses or CSS syntax; trims outer whitespace and preserves quoted text.
How to use the tool and how it works
- Enter value using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.tokens. Use the ordering, boundary rules and absence conditions described below.
Split at top-level commas while respecting quoted strings and angle-bracket regions, then trim each resulting token.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| value | Field-value text under the stated supported character and splitting rules. | Text, at most 8,192 UTF-16 code units; the operation’s grammar also applies. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.tokens | Trimmed top-level comma-separated token spellings. |
{
"input": {
"value": "a, \"b,c\", d"
},
"output": {
"result": {
"tokens": [
"a",
"\"b,c\"",
"d"
]
}
}
}Limitations and assumptions
- Empty tokens can remain and no field-specific list semantics or negotiation is applied.
- Explicit header records have name and value strings. Names must use token syntax; supported value code units are tab or 32–255 excluding DEL. Byte budgets use that single-byte representation, not UTF-8 or HTTP/2 compression.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Choose field-specific parsing and combination rules rather than applying one policy to every header. Preserve occurrence order and use a full HTTP implementation for message framing and protocol-level decisions.
References
-
RFC 9110: HTTP Semantics — RFC Editor
-
Tool behavior and example: HTTP Header Top-Level Comma Token Splitter — tool.io
Similar or alternative tools
- HTTP Header Line First Colon Splitter
Split one HTTP field line at its first colon, validating a nonempty token name while retaining raw value whitespace; CR/LF or obs-fold are rejected.
- HTTP Header Quoted Token Source Map
Map complete HTTP quoted-string source spans and decoded quoted-pair values; token contents are Latin-1/HTAB and unclosed escapes/strings reject.