Description
Return valid only when zone equals the exact uppercase token GMT, and return canonical as GMT for that case or empty text otherwise.
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.
Return valid only when zone equals the exact uppercase token GMT, and return canonical as GMT for that case or empty text otherwise.
When to use this tool
Use HTTP Date IMF Fixdate Zone 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 zone. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, canonical. Inspect valid before interpreting the associated values.
Return valid only when zone equals the exact uppercase token GMT, and return canonical as GMT for that case or empty text otherwise.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| zone | Zone | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this tool’s particular check passes; does not imply broader identifier or protocol validity. | Required. Boolean. |
| canonical | Canonical spelling under this tool’s formatting rule; inspect validity flags separately. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"zone": "GMT"
},
"output": {
"valid": true,
"canonical": "GMT"
}
}Limitations and assumptions
- The empty canonical value accompanies a successful false result. This checks one zone token without validating a complete HTTP date or converting a local time.
- 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
- Web: HTTP Age Date Response Adjustment
Apply RFC9111 apparent-age/response-delay adjustment and resident time from explicit parsed timestamps and Age; not a cache freshness or header parser.
- HTTP Date Precision Tie
Compare already-normalized whole-second HTTP date values, without parsing obsolete date formats.