Description
Decode the restricted form-data space/plus token distinction.
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 the restricted form-data space/plus token distinction.
When to use this tool
Use URL Form Plus Space Token when decoding one explicitly supported format fragment.
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 text. Use the output convention below.
Decode the restricted form-data space/plus token distinction. Accept only +, %2B or %2b; literal plus becomes space and escaped plus becomes plus.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| text | Text | Required. Text; maximum UTF-16 length 8192. |
json
{
"input": {
"token": "+"
},
"output": {
"text": " "
}
}Limitations and assumptions
- This is not generic URL decoding or a whole application/x-www-form-urlencoded parser.
- 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
- RFC 2047 Q Underscore Space Token
Decode one RFC 2047 Q-space token.
- Utf16 Lone Surrogate Token Label
Classify a numeric UTF-16 code unit.