Description
Match token as case-insensitive max-stale, optionally followed by equals and unsigned digits.
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.
Match token as case-insensitive max-stale, optionally followed by equals and unsigned digits.
When to use this tool
Use HTTP Cache Control Maxstale Unbounded 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 token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read unbounded, seconds. Inspect unbounded before interpreting the associated values.
Match token as case-insensitive max-stale, optionally followed by equals and unsigned digits. Return unbounded when no value is present; otherwise parse seconds as a nonnegative safe integer, with zero used for the valueless form.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| unbounded | Unbounded | Required. Boolean. |
| seconds | Parsed nonnegative safe-integer seconds; zero is a placeholder when unbounded is true. | Required. Safe integer. |
{
"input": {
"token": "max-stale"
},
"output": {
"unbounded": true,
"seconds": 0
}
}Limitations and assumptions
- Unbounded distinguishes a missing value from an explicit zero. No spaces or quoted numbers are admitted by this token parser, and cache reuse or other directives are not 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
- Cache Control Private Field Name Token
Extract lowercased field-name tokens from a quoted Cache-Control private field list.
- HTTP Age Cache Freshness Residual
Calculate remaining cache freshness lifetime and mark exact lifetime equality as no longer fresh.