URL Fragment Empty Marker Tool

Description

Find the first literal hash in url.

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.

Find the first literal hash in url.

When to use this tool

Use URL Fragment Empty 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 url. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read present, empty, fragment. Inspect present, empty before interpreting the associated values.

Find the first literal hash in url. Return present, whether that delimiter is the final character as empty, and the entire following substring as fragment.^[1]

Input field	Meaning and units	Accepted input
url	Url	Required. Text; maximum UTF-16 length 8192.

Output field	Interpretation	Returned shape
present	Present	Required. Boolean.
empty	Whether a present first hash ends the supplied text.	Required. Boolean.
fragment	Text after the first hash, including any later hashes.	Required. Text; maximum UTF-16 length 8192.

json

{
  "input": {
    "url": "https://example.com/#"
  },
  "output": {
    "present": true,
    "empty": true,
    "fragment": ""
  }
}

Limitations and assumptions

Absent and empty fragments both have empty fragment text but different flags. Later hashes remain fragment content; the string is not parsed or validated as a URL.
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

Calculation and input contract: web/url-fragment-empty-marker — tool.io

Similar or alternative tools

URI Fragment Empty State
Distinguish absent, empty and nonempty literal URI fragment components without percent decoding.
web/url-hash
A fragment identifies a part or client-side state of a resource after a hash.