Description
Validate encodings against the implemented token subset and require a zero-based index within the 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.
Validate encodings against the implemented token subset and require a zero-based index within the list.
When to use this tool
Use HTTP Content Encoding Order Index 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 encodings, index. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read encoding, decodeIndex. Use the output convention below.
Validate encodings against the implemented token subset and require a zero-based index within the list. Return that encoding lowercased and decodeIndex=list length-1-index.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| encodings | Encodings | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| index | Zero-based index unless a different convention is explicitly stated. | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| encoding | Encoding | Required. Text; maximum UTF-16 length 8192. |
| decodeIndex | Decode Index | Required. Safe integer. |
{
"input": {
"encodings": [
"gzip",
"br"
],
"index": 0
},
"output": {
"encoding": "gzip",
"decodeIndex": 1
}
}Limitations and assumptions
- The list is supplied in encoding-application order, so decodeIndex expresses its reverse. The token subset excludes apostrophes; no encoding implementation, payload decoding, or complete header parser is provided.
- 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 Content Length Leading Zero Canonicalizer
Canonicalize a digit-only Content-Length token as exact decimal text without leading zeros.
- HTTP Content Range Length Consistency
Compare an inclusive byte range's computed length with a supplied payload length.