Description
Extract lowercased field-name tokens from a quoted Cache-Control private field list.
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.
Extract lowercased field-name tokens from a quoted Cache-Control private field list.
When to use this tool
Use Cache Control Private Field Name Token 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 fields. Use the output convention below.
Require the complete case-insensitive private="..." form. Split the quoted contents on commas, trim and lowercase each field name, require valid nonempty token spellings, and return fields in supplied order.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| value | Value | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| fields | Fields | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
{
"input": {
"value": "private=\"Set-Cookie, X-Test\""
},
"output": {
"fields": [
"set-cookie",
"x-test"
]
}
}Limitations and assumptions
- Duplicates remain and an empty list is rejected. JavaScript trimming is broader than HTTP whitespace; no other Cache-Control directives, shared-cache storage, or actual message fields are evaluated.
- 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
- HTTP Cache Control Maxstale Unbounded Token
Match token as case-insensitive max-stale, optionally followed by equals and unsigned digits.
- Cache Directive Delta Seconds Boundary
Return a delta-seconds token's exact decimal value and a numeric interpretation capped at 2147483648.