Description
Decode one percent triplet to an octet.
Escaping and token decoding depend on the surrounding format. Form-data plus signs, MIME Q underscores, quoted-printable octets and quoted CSV fragments have different meanings even when their text looks similar.
Decode one percent triplet to an octet.
When to use this tool
Use Decoding: Percent Encoded Octet Triplet when decoding one explicitly supported format fragment.
How to use the tool and how it works
- Enter triplet. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Decode one percent triplet to an octet. Require percent followed by exactly two case-insensitive hexadecimal digits; return the parsed byte value.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| triplet | Triplet | Required. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Returned object; expand its named members below. | Required. Object. |
| result.octet | One numeric octet, from 0 through 255. | Calculated result member: number. |
{
"input": {
"triplet": "%FF"
},
"output": {
"result": {
"octet": 255
}
}
} Limitations and assumptions
- No UTF-8 conversion, URL component interpretation or whole-string decoding is performed.
- Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use the full format-specific parser for framing, context, charset conversion and complete data validation.
References
Similar or alternative tools
- Quoted Printable Hex Pair Octet
Decode one quoted-printable hexadecimal octet token.
- RFC 2047 Encoded Word Header Fields
Split a restricted MIME encoded-word into header fields.