Description
Decode one supplied query component with an explicit literal-plus versus form-space policy.
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.
Decode one supplied query component with an explicit literal-plus versus form-space policy.
When to use this tool
Use URI Query Plus Literal Policy 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 query, plusPolicy. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read value. Use the output convention below.
Decode query with decodeURIComponent, either preserving plus signs under literal policy or replacing them with spaces first under form-space. Reject unsupported policies and malformed percent-encoded UTF-8, returning value.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| query | Query | Required. Text; maximum UTF-16 length 8192. |
| plusPolicy | literal preserves plus signs; form-space replaces them with spaces before percent decoding. | Required. Text; one of "literal", "form-space"; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| value | Value | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"query": "a+b%2Bc",
"plusPolicy": "literal"
},
"output": {
"value": "a+b+c"
}
}Limitations and assumptions
- The entire supplied component is decoded as one string; ampersands and equals signs are not parsed into parameters. The plus policy is explicit rather than inferred from a URL or content type.
- 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 Query Empty Value Equals Marker
Split token at its first equals sign into name and value, returning hasEquals.
- parse/url
Split an absolute hierarchical URL into protocol, host, port, path, query, and fragment components. Bracketed IPv6 hosts and user-info prefixes are supported.