client =
      OkHttpClient
        .Builder()
        .proxy(server.proxyAddress)
        .build()
    server.enqueue(MockResponse(body = "abc"))
    server.enqueue(MockResponse(body = "def"))
    server.enqueue(MockResponse(body = "ghi"))
    client = client.newBuilder().build()
    executeSynchronously("/a").assertBody("abc")
    client = client.newBuilder().build()

// In PropertyConfiguration.java
public static final String USE_WITNESS = "jcifs.smb.client.useWitness";
public static final String WITNESS_HEARTBEAT_TIMEOUT = "jcifs.smb.client.witnessHeartbeatTimeout";
public static final String WITNESS_REGISTRATION_TIMEOUT = "jcifs.smb.client.witnessRegistrationTimeout";
public static final String WITNESS_RECONNECT_DELAY = "jcifs.smb.client.witnessReconnectDelay";

    )
    server.enqueue(
      MockResponse(body = "Successful auth!"),
    )
    val credential = basic("username", "password")
    client =
      client
        .newBuilder()
        .authenticator(RecordingOkAuthenticator(credential, "Basic"))
        .build()
    val call = client.newCall(Request(server.url("/")))
    val response = call.execute()
    assertThat(response.body.string()).isEqualTo("Successful auth!")

    }

    /**
     * Checks if the client is connected to the witness service.
     *
     * @return true if connected
     */
    public boolean isConnected() {
        return connected && rpcHandle != null;
    }

    @Override
    public void close() {
        if (connected && rpcHandle != null) {
            try {
                log.debug("Closing witness RPC client");
                rpcHandle.close();

# Fehlerbehandlung

Es gibt viele Situationen, in denen Sie einem Client, der Ihre API benutzt, einen Fehler zurückgeben müssen.

Dieser Client könnte ein Browser mit einem Frontend, Code von jemand anderem, ein <abbr title="Internet of Things – Internet der Dinge: Geräte, die über das Internet Informationen austauschen">IoT</abbr>-Gerät, usw., sein.

Sie müssten beispielsweise einem Client sagen:

$ npm run generate-client

frontend-app@1.0.0 generate-client /home/user/code/frontend-app
> openapi-ts --input http://localhost:8000/openapi.json --output ./src/client --client axios
```

</div>

Ese comando generará código en `./src/client` y usará `axios` (el paquete HTTP de frontend) internamente.

### Prueba el Código del Cliente

                return Collections.emptyList();
            }
        };
        ComponentUtil.register(client, "searchEngineClient");
        final DocList docList = new DocList();
        indexingHelper.sendDocuments(client, docList);
        assertEquals(0, docList.size());
        assertEquals(0, sentDocList.size());
        assertNull(sentIndex.get());

    }

    /**
     * Creates a new witness client with a custom RPC client (for testing).
     *
     * @param witnessServer the witness server address
     * @param context the CIFS context
     * @param rpcClient the RPC client to use
     */
    protected WitnessClient(InetAddress witnessServer, CIFSContext context, WitnessRpcClient rpcClient) {

# MinIO FTP/SFTP Server

MinIO natively supports FTP/SFTP protocol, this allows any ftp/sftp client to upload and download files.

Currently supported `FTP/SFTP` operations are as follows:

| ftp-client commands | supported |
|:-------------------:|:----------|
| get                 | yes       |
| put                 | yes       |
| ls                  | yes       |
| mkdir               | yes       |
| rmdir               | yes       |

```console
$ npm run generate-client

frontend-app@1.0.0 generate-client /home/user/code/frontend-app
> openapi-ts --input http://localhost:8000/openapi.json --output ./src/client --client axios
```

</div>

Dieser Befehl generiert Code in `./src/client` und verwendet intern `axios` (die Frontend-HTTP-Bibliothek).

### Den Client-Code ausprobieren