HTTP Quality Thousandths Parser
Parse strict HTTP qvalue syntax into exact integer thousandths; no signs, exponent, whitespace or more than three decimals.
Description
Parse strict HTTP qvalue syntax into exact integer thousandths; no signs, exponent, whitespace or more than three decimals.
A quality-value token has a stricter grammar than a general decimal between zero and one.1
When to use this tool
Parse strict HTTP qvalue syntax into exact integer thousandths; no signs, exponent, whitespace or more than three decimals.
- 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.thousandths. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require the RFC-style zero-or-one spelling with an optional dot and at most three fractional digits, allowing only zeros after one. Convert to integer thousandths.2
| 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.thousandths | The thousandths value under the stated formula or text convention. |
{
"input": {
"value": "0.125"
},
"output": {
"result": {
"thousandths": 125
}
}
}Limitations and assumptions
- Whitespace, signs, exponents and a leading decimal point are rejected. Values such as 0. and 1. are accepted by the implemented grammar; no complete header is parsed.
- 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
-
RFC 9110: Quality values — RFC Editor
-
Tool behavior and example: HTTP Quality Thousandths Parser — tool.io
Similar or alternative tools
- HTTP Quality Thousandths Formatter
Format integer quality thousandths as a minimal RFC qvalue spelling between zero and one.
- HTTP Content Length Decimal Parser
Parse Content-Length as exact unsigned ASCII decimal text without unsafe numeric conversion, signs, whitespace or exponent syntax.