Description
Classify one ASCII byte under the RFC 3986 unreserved set.
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.
Classify one ASCII byte under the RFC 3986 unreserved set.
When to use this tool
Use Percent Encoding Unreserved Flag 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 byte. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read unreserved, literal. Inspect unreserved before interpreting the associated values.
Require an integer ASCII byte from zero through 127. Return literal as its single character and unreserved true only for letters, digits, hyphen, dot, underscore, or tilde.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| byte | Integer ASCII byte from zero through 127; includes control bytes. | Required. Safe integer; minimum 0; maximum 127. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| unreserved | Unreserved | Required. Boolean. |
| literal | Single-character string for the byte; controls may require escaping when displayed. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"byte": 65
},
"output": {
"unreserved": true,
"literal": "A"
}
}Limitations and assumptions
- ASCII controls are accepted as bytes and can appear escaped in a serialized literal, but are not unreserved. This does not encode a string, validate UTF-8, or authorize a character in every URL component.
- 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
- URI Unreserved Percent Normalization
Normalize one percent escape by decoding an unreserved ASCII character or uppercasing the preserved escape.
- URI Percent Triplet Ascii Check
Check token for exactly one percent sign and two hexadecimal digits.