URL Path Empty Segment Profile

Profile raw literal URL-path empty segments without URL normalization or decoding escaped slashes.

Description

Profile raw literal URL-path empty segments without URL normalization or decoding escaped slashes.

Empty raw URL path segments can represent leading, repeated or terminal slashes. Keeping them prevents information loss.

When to use this tool

Profile raw literal URL-path empty segments without URL normalization or decoding escaped slashes.

Prepare the supplied path fields for this operation.
Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

Enter path. Use the exact text syntax, units and index conventions explained below.
Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
Read result.segments, result.emptyIndexes, result.leadingSlash, result.trailingSlash. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Reject query and fragment characters, split path literally on slash and return segments, emptyIndexes and leading/trailing slash flags.^[1]

Input field	Meaning and representation	Accepted input
path	path.	Text; at most 8,192 UTF-16 code units, subject to the grammar above

Output field	Interpretation
result	Object containing the named outputs below.
result.segments	The segments list in the ordering and representation described above.
result.emptyIndexes	The empty indexes list in the ordering and representation described above.
result.leadingSlash	Flag for leading slash under the exact condition described above.
result.trailingSlash	Flag for trailing slash under the exact condition described above.

json

{
  "input": {
    "path": "/a//b/"
  },
  "output": {
    "result": {
      "segments": [
        "",
        "a",
        "",
        "b",
        ""
      ],
      "emptyIndexes": [
        0,
        2,
        4
      ],
      "leadingSlash": true,
      "trailingSlash": true
    }
  }
}

Limitations and assumptions

Empty path produces one empty segment with both flags false. No percent-decoding, dot removal or URL parsing is performed.
Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
String lists have at most 128 entries of at most 128 code units; matrices have at most 128 rows and columns. Larger numeric lists and parsed JSON have separate bounded budgets. Nonfinite results and excessively large serialized outputs are rejected.
Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Use a complete protocol or URL parser when interpreting a whole message or address. Preserve raw spelling when required and distinguish HTTP token grammar, URL path normalization and form-style query decoding.

References

Tool behavior and example: URL Path Empty Segment Profile — tool.io

Similar or alternative tools

URL Dot Segment Event Trace
Trace RFC 3986 section 5.2.4 literal URL dot-segment removal, preserving meaningful empty slash segments. Percent-encoded dots and slashes remain opaque; not complete URI reference resolution, authorization or filesystem traversal protection.
URL Path Prefix Token Match
Check a literal raw URL-path segment prefix, retaining empty segments and rejecting accidental character-prefix matches.