Description
Extract an exact decimal total from the unsatisfied Content-Range form bytes */total.
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 an exact decimal total from the unsatisfied Content-Range form bytes */total.
When to use this tool
Use HTTP Content Range Unsatisfied Total 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 header. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read total. Use the output convention below.
Require header to match the exact bytes */total spelling with a canonical nonnegative decimal total of at most 128 digits. Return total as text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| header | Header | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| total | Total | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"header": "bytes */123"
},
"output": {
"total": "123"
}
}Limitations and assumptions
- Zero is accepted, while leading zeros in a multi-digit total are rejected. This handles only an unsatisfied byte-range form, without deciding an HTTP status or validating a complete response.
- 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 Range Length Consistency
Compare an inclusive byte range's computed length with a supplied payload length.
- HTTP Content Encoding Order Index
Validate encodings against the implemented token subset and require a zero-based index within the list.