Description
Normalize one percent escape by decoding an unreserved ASCII character or uppercasing the preserved escape.
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.
Normalize one percent escape by decoding an unreserved ASCII character or uppercasing the preserved escape.
When to use this tool
Use URI Unreserved Percent Normalization 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 token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read normalized, decoded. Inspect decoded before interpreting the associated values.
Require exactly one percent sign followed by two hexadecimal digits. Decode its byte only when it is an ASCII letter, digit, hyphen, dot, underscore, or tilde; otherwise preserve the escape with uppercase hex digits. Return normalized and decoded.1
The URI unreserved set consists of ASCII letters, digits, hyphen, dot, underscore, and tilde.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| normalized | Normalized | Required. Text; maximum UTF-16 length 8192. |
| decoded | Decoded | Required. Boolean. |
{
"input": {
"token": "%7e"
},
"output": {
"normalized": "~",
"decoded": true
}
}Limitations and assumptions
- This handles one escape token rather than an entire URI or UTF-8 sequence. Reserved characters remain escaped and the operation does not establish URL validity or resource equivalence.
- 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
- Percent Encoding Unreserved Flag
Classify one ASCII byte under the RFC 3986 unreserved set.
- URI Percent Triplet Ascii Check
Check token for exactly one percent sign and two hexadecimal digits.