Description
Witness complete containment of an inclusive byte range; zero witness endpoints are unused when containment is false.
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.
Witness complete containment of an inclusive byte range; zero witness endpoints are unused when containment is false.
When to use this tool
Use HTTP Range Complete Overlap Witness 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 start, end, otherStart, otherEnd. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read contained, witnessStart, witnessEnd. Inspect contained before interpreting the associated values.
Require ordered nonnegative integer start/end and otherStart/otherEnd pairs. Set contained only when the first interval lies wholly inside the other; then return the first interval as witnessStart and witnessEnd, otherwise return zero placeholders.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| start | Start | Required. Safe integer; minimum 0. |
| end | End | Required. Safe integer. |
| otherStart | Other Start | Required. Safe integer; minimum 0. |
| otherEnd | Other End | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| contained | Contained | Required. Boolean. |
| witnessStart | Start of the contained interval when contained is true, otherwise zero placeholder. | Required. Safe integer. |
| witnessEnd | End of the contained interval when contained is true, otherwise zero placeholder. | Required. Safe integer. |
{
"input": {
"start": 10,
"end": 20,
"otherStart": 0,
"otherEnd": 30
},
"output": {
"contained": true,
"witnessStart": 10,
"witnessEnd": 20
}
}Limitations and assumptions
- This tests complete containment, not every nonempty overlap. When contained is false the witness zeros are not an actual overlap interval; resource length and HTTP header syntax are not checked.
- 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 Range Unsatisfied Total
Extract an exact decimal total from the unsatisfied Content-Range form bytes */total.