Description
Split value around the first two apostrophe-delimited fields into charset, language, and encodedValue, requiring a nonempty whitespace-free charset and no carriage return or newline.
Web protocol data has several layers: a complete message or URL, individual fields or components, and the literal tokens within them. Delimiter presence, spelling, comparison rules, and parser normalization can affect results. A check of one component needs its stated scope before it can be used in a larger parser or policy decision.
Split value around the first two apostrophe-delimited fields into charset, language, and encodedValue, requiring a nonempty whitespace-free charset and no carriage return or newline.
When to use this tool
Use Content Disposition RFC 5987 Language Field when you need one stated URL, header, or protocol-component check in a diagnostic or parser workflow. Supply the input level specified below.
How to use the tool and how it works
- Enter value. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read charset, language, encodedValue. Use the output convention below.
Split value around the first two apostrophe-delimited fields into charset, language, and encodedValue, requiring a nonempty whitespace-free charset and no carriage return or newline.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| value | Value | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| charset | Charset | Required. Text; maximum UTF-16 length 8192. |
| language | Language | Required. Text; maximum UTF-16 length 8192. |
| encodedValue | Encoded Value | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"value": "UTF-8'en'report%20one.txt"
},
"output": {
"charset": "UTF-8",
"language": "en",
"encodedValue": "report%20one.txt"
}
}Limitations and assumptions
- The language may be empty. Charset support, language-tag validity, percent encoding, byte decoding, and a complete Content-Disposition field are not validated.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
Alternative or Complementary methods
Use a complete URL or header parser when the task involves an entire field or message. Test actual browser, server, or cache behavior separately when a security or protocol decision depends on more than this component.
References
Similar or alternative tools
- Cache Control Private Field Name Token
Extract lowercased field-name tokens from a quoted Cache-Control private field list.
- Content Security Policy Report Only Label
Lowercase headerName and return recognized for content-security-policy or content-security-policy-report-only.