HTTP Content Length Decimal Parser

Parse Content-Length as exact unsigned ASCII decimal text without unsafe numeric conversion, signs, whitespace or exponent syntax.

Description

Parse Content-Length as exact unsigned ASCII decimal text without unsafe numeric conversion, signs, whitespace or exponent syntax.

An HTTP decimal length can be kept exact as canonical digit text even beyond ordinary integer precision.

When to use this tool

Parse Content-Length as exact unsigned ASCII decimal text without unsafe numeric conversion, signs, whitespace or exponent syntax.

Prepare the supplied value fields for this operation.
Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

Enter value. Use the exact text syntax, units and index conventions explained below.
Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
Read result.canonicalDecimal. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require value to consist only of one or more ASCII digits, then remove leading zeros while retaining one zero for an all-zero value. Return canonicalDecimal.^[1]

Input field	Meaning and representation	Accepted input
value	value.	Text; at most 8,192 UTF-16 code units, subject to the grammar above

Output field	Interpretation
result	Object containing the named outputs below.
result.canonicalDecimal	The canonical decimal value under the stated formula or text convention.

json

{
  "input": {
    "value": "00042"
  },
  "output": {
    "result": {
      "canonicalDecimal": "42"
    }
  }
}

Limitations and assumptions

No surrounding whitespace, sign, comma list or unit suffix is accepted. The parser does not count body bytes or validate message framing.
Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. Nonfinite results and excessively large serialized outputs are rejected.
Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Use a complete protocol or URL parser when interpreting a whole message or address. Preserve raw spelling when required and distinguish HTTP token grammar, URL path normalization and form-style query decoding.

References

Tool behavior and example: HTTP Content Length Decimal Parser — tool.io

Similar or alternative tools

HTTP Content Length List Consistency
Audit comma-combined Content-Length decimal members for exact numeric consistency after OWS trimming; does not accept empty members.
HTTP Quality Thousandths Parser
Parse strict HTTP qvalue syntax into exact integer thousandths; no signs, exponent, whitespace or more than three decimals.