Description
Parse first and last as bounded exact decimal integers and require both nonnegative.
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.
Parse first and last as bounded exact decimal integers and require both nonnegative.
When to use this tool
Use HTTP Range Invalid Endpoint Order 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. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, length. Inspect valid before interpreting the associated values.
Parse first and last as bounded exact decimal integers and require both nonnegative. Return valid when first<=last and length=last-first+1 as decimal text; reversed endpoints return valid false and length zero.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| first | First | Required. Text; maximum UTF-16 length 8192. |
| last | Last | 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. |
| length | Length | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"first": "10",
"last": "19"
},
"output": {
"valid": true,
"length": "10"
}
}Limitations and assumptions
- This checks one inclusive endpoint pair without parsing a Range header or comparing with a representation's length. A successful false result is distinct from malformed decimal input.
- 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 Encoding Order Index
Validate encodings against the implemented token subset and require a zero-based index within the list.
- HTTP Content Range Length Consistency
Compare an inclusive byte range's computed length with a supplied payload length.