* Normalize a path
     */
    private String normalizePath(String path) {
        // Replace forward slashes with backslashes for consistency
        String normalized = path.replace('/', '\\');

        // Remove duplicate slashes
        normalized = normalized.replaceAll("\\\\+", "\\\\");

        // Remove trailing slash unless it's the root
        if (normalized.length() > 1 && normalized.endsWith("\\")) {

   * Additionally, the escaper escapes the slash character ("/"). While slashes are acceptable in
   * URL paths, they are considered by the specification to be separators between "path segments."
   * This implies that, if you wish for your path to contain slashes, you must escape each segment
   * separately and then join them.
   *

   * Additionally, the escaper escapes the slash character ("/"). While slashes are acceptable in
   * URL paths, they are considered by the specification to be separators between "path segments."
   * This implies that, if you wish for your path to contain slashes, you must escape each segment
   * separately and then join them.
   *

    assertThat(
      base
        .newBuilder()
        .addPathSegments("/d")
        .build()
        .encodedPath,
    ).isEqualTo("/a/b/c//d")

    // Add a string with two slashes: resulting URL gains three slashes.
    assertThat(
      base
        .newBuilder()
        .addPathSegments("//")
        .build()
        .encodedPath,
    ).isEqualTo("/a/b/c///")
    assertThat(

     */
    public static String normalizeSmbPath(String path) {
        validateSmbPath(path);

        // Normalize slashes
        path = path.replace('/', '\\');

        // Remove redundant slashes
        path = path.replaceAll("\\\\+", "\\\\");

        // Remove trailing slash unless it's root
        if (path.length() > 1 && path.endsWith("\\")) {
            path = path.substring(0, path.length() - 1);

     *   <li>Other sources may not support resolution and return null</li>
     * </ul>
     * <p>
     * The implementation must handle:
     * <ul>
     *   <li>Both forward and back slashes as path separators</li>
     *   <li>Parent directory references (..)</li>
     *   <li>Both file and directory targets</li>
     * </ul>
     *
     * @param relative path to resolve relative to this source

    void testVariousFilenameFormats() {
        // Test UNC path
        assertDoesNotThrow(() -> new Trans2GetDfsReferral(mockConfig, "\\\\server\\share"));

        // Test forward slashes
        assertDoesNotThrow(() -> new Trans2GetDfsReferral(mockConfig, "//server/share"));

        // Test with spaces
        assertDoesNotThrow(() -> new Trans2GetDfsReferral(mockConfig, "\\\\server\\my share\\file.txt"));

        /* Samba has a tendency to return referral paths and pathConsumed values
         * in such a way that there can be a slash at the end of the path. This
         * causes problems matching keys in resolve() where an extra slash causes
         * a mismatch. This strips trailing slashes from all keys to eliminate
         * this problem.
         */
        int ki = key.length();

 * Both the unnecessary port specification (`:80`) and the absent trailing slash (`/`) cause URI to
 * bucket the two URLs separately. This harms URI's usefulness in collections. Any application that
 * stores information-per-URL will need to either canonicalize manually, or suffer unnecessary
 * redundancy for such URLs.
 *
 * Because they don't attempt canonical form, these classes are surprisingly difficult to use

   *
   * <ul>
   *   <li>empty string becomes .
   *   <li>. stays as .
   *   <li>fold out ./
   *   <li>fold out ../ when possible
   *   <li>collapse multiple slashes
   *   <li>delete trailing slashes (unless the path is just "/")
   * </ul>
   *
   * <p>These heuristics do not always match the behavior of the filesystem. In particular, consider