Description
Compare an inclusive byte range's computed length with a supplied payload length.
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.
Compare an inclusive byte range's computed length with a supplied payload length.
When to use this tool
Use HTTP Content Range Length Consistency 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 first, last, total, payloadLength. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read rangeLength, consistent. Inspect consistent before interpreting the associated values.
Require nonnegative integer first and payloadLength, last>=first, and total>last. Return rangeLength=last-first+1 and consistent when it equals payloadLength.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| first | First | Required. Safe integer; minimum 0. |
| last | Last | Required. Safe integer. |
| total | Total | Required. Safe integer. |
| payloadLength | Supplied payload byte count, not bytes read by the tool. | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| rangeLength | Range Length | Required. Safe integer. |
| consistent | Consistent | Required. Boolean. |
{
"input": {
"first": 10,
"last": 19,
"total": 100,
"payloadLength": 10
},
"output": {
"rangeLength": 10,
"consistent": true
}
}Limitations and assumptions
- The interval is inclusive and must fit the supplied total. The tool compares a supplied byte count, without reading a body, parsing Content-Range, or deciding whether a server response is correct overall.
- 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 Unsatisfied Total
Extract an exact decimal total from the unsatisfied Content-Range form bytes */total.