Description
Split token at its first equals sign into name and value, returning hasEquals.
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.
Split token at its first equals sign into name and value, returning hasEquals.
When to use this tool
Use URI Query Empty Value Equals Marker 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 name, value, hasEquals. Inspect hasEquals before interpreting the associated values.
Split token at its first equals sign into name and value, returning hasEquals. With no equals sign preserve the token as name and return empty value; reject ampersand, hash, and question mark.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| name | Name | Required. Text; maximum UTF-16 length 8192. |
| value | Value | Required. Text; maximum UTF-16 length 8192. |
| hasEquals | Has Equals | Required. Boolean. |
{
"input": {
"token": "flag="
},
"output": {
"name": "flag",
"value": "",
"hasEquals": true
}
}Limitations and assumptions
- This preserves the distinction between a bare name and an explicit empty value. Extra equals signs stay in value, and neither percent decoding nor plus conversion is performed.
- 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 Plus Literal Policy
Decode one supplied query component with an explicit literal-plus versus form-space policy.
- Web: URL Empty Query Vs Absent Label
Distinguish an absent query from an explicitly present empty query in a valid absolute HTTP(S) URL, preserving lexical question marks before the fragment.