Description
Distinguish absent, empty and nonempty literal URI fragment components without percent decoding.
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.
Distinguish absent, empty and nonempty literal URI fragment components without percent decoding.
When to use this tool
Use URI Fragment Empty State 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 uriReference. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read state, fragment, delimiterIndex. Use the output convention below.
Find the first hash in uriReference and return state as absent, empty, or nonempty, along with fragment and zero-based delimiterIndex; absent uses index minus one.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| uriReference | Uri Reference | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| state | State | Required. Text; maximum UTF-16 length 8192. |
| fragment | Fragment | Required. Text; maximum UTF-16 length 8192. |
| delimiterIndex | Zero-based position of the first hash, or minus one when absent. | Required. Safe integer. |
{
"input": {
"uriReference": "page#"
},
"output": {
"state": "empty",
"fragment": "",
"delimiterIndex": 4
}
}Limitations and assumptions
- The states describe literal delimiter presence, not a parsed URI's validity. Percent escapes are unchanged, and additional hashes remain within the returned fragment.
- 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
- URL Fragment Empty Marker
Find the first literal hash in url.
- web/url-hash
A fragment identifies a part or client-side state of a resource after a hash.