Description
Parse an HTTP name and double-quoted parameter value, lowercasing the name and removing supported backslash escapes.
HTTP fields use specific token, quoted-string, range, quality-weight, and entity-tag grammars. Quoted text is not automatically safe as a filename or equivalent to an escaped string in another language. Parsing one parameter or marker is separate from interpreting a full request or response.
Parse an HTTP name and double-quoted parameter value, lowercasing the name and removing supported backslash escapes.
When to use this tool
Use HTTP Link Parameter Single Quoted Token when you need to parse this one supported HTTP field component or parameter token.
How to use the tool and how it works
- Enter parameter. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read name, value. Use the output convention below.
Accept a token parameter name followed immediately by = and a double-quoted value with supported backslash-escaped printable characters. Lowercase name and remove quoting/backslash escapes from value.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| parameter | Name="value" with a double-quoted value, despite the tool name. | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| name | Name | Required. Text; maximum UTF-16 length 8192. |
| value | Value | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"parameter": "title=\"report one\""
},
"output": {
"name": "title",
"value": "report one"
}
}Limitations and assumptions
- Despite the tool name, it expects a double-quoted parameter value rather than single-quote delimiters. It does not parse a Link header, resolve a target, decode extended values, or comprehensively validate HTTP field octets.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use a full header parser and the relevant HTTP semantics when request behavior depends on the result. Check extended parameters, field context, and downstream use of returned text separately.
References
Similar or alternative tools
- Parsing: Mime Quoted Parameter Unescape
Unescape one restricted ASCII MIME quoted-string parameter, honoring quoted-pair escapes and rejecting raw quotes, controls and line folding.
- HTTP Contentdisposition Filename Parameter
Unescape backslash pairs in quoted values and return filename and quoted.