URL Path Empty Segment Count Tool

Description

Count literal empty slash-delimited path segments with explicit endpoint inclusion; do not parse a full 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.

Count literal empty slash-delimited path segments with explicit endpoint inclusion; do not parse a full URL.

When to use this tool

Use URL Path Empty Segment Count 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 path, includeLeading, includeTrailing. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read emptySegments. Use the output convention below.

Split path on slash and count empty segments, excluding the first empty segment unless includeLeading and the final empty segment unless includeTrailing.^[1]

Input field	Meaning and units	Accepted input
path	Path	Required. Text; maximum UTF-16 length 8192.
includeLeading	Include Leading	Required. Boolean.
includeTrailing	Include Trailing	Required. Boolean.

Output field	Interpretation	Returned shape
emptySegments	Empty Segments	Required. Safe integer.

json

{
  "input": {
    "path": "/a//b/",
    "includeLeading": false,
    "includeTrailing": false
  },
  "output": {
    "emptySegments": 1
  }
}

Limitations and assumptions

For an empty path, the sole segment is both first and last and counts only when both flags are true. Percent-encoded slashes are not decoded and dot segments are not normalized.
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-path-empty-segment-count — tool.io

Similar or alternative tools

web/url-path-empty-segment-profile
Profile raw literal URL-path empty segments without URL normalization or decoding escaped slashes.
URI Query Empty Value Equals Marker
Split token at its first equals sign into name and value, returning hasEquals.