final Properties p = new Properties();
        p.putAll(System.getProperties());
        /*
         * Set jcifs properties we know we want; soTimeout and cachePolicy to 10min.
         */
        p.setProperty("jcifs.smb.client.soTimeout", "300000");
        p.setProperty("jcifs.netbios.cachePolicy", "600");

        final Enumeration<String> e = config.getInitParameterNames();
        String name;

					if err := healFreshDisk(ctx, z, disk); err != nil {
						globalBackgroundHealState.setDiskHealingStatus(disk, false)
						timedout := OperationTimedOut{}
						if !errors.Is(err, context.Canceled) && !errors.As(err, &timedout) && !errors.Is(err, errRetryHealing) {
							printEndpointError(disk, err, false)
						}
						return
					}
					// Only upon success pop the healed disk.

A single HTTP call may require follow-up requests to be made to handle authentication challenges, redirects, and HTTP-layer timeouts. In such cases multiple connections, requests, and responses may be attempted. Follow-ups are another reason a single call may trigger multiple events of the same type.

        significant if you have many PS servers. We are aware of this issue and
        working on fixes, for now we suggest using the legacy optimizers when
        using `ParameterServerStrategy`.
    *   **Timeout or performance loss.** We don't anticipate this to happen, but
        if you see such issues, please use the legacy optimizer, and file
        an issue in the Keras GitHub repo.

	<component name="internalHttpClient" class="org.codelibs.fess.crawler.client.http.HcHttpClient"
		instance="prototype">
		<property name="connectionTimeout">15000</property>
		<property name="soTimeout">30000</property>
	</component>
	<component name="httpClient"
		class="org.codelibs.fess.crawler.client.FaultTolerantClient" instance="prototype">
		<property name="crawlerClient">internalHttpClient</property>

  .addHeader("Cache-Control", "no-cache")
  .body("{}")
  .build()
```

MockResponse can be used to simulate a slow network. This is useful for
testing timeouts and interactive testing.

### Java
```java
MockResponse response = new MockResponse.Builder()
    .throttleBody(1024, 1, TimeUnit.SECONDS)
    .build();
```

### Kotlin
```kotlin

        String name;

        final Properties p = new Properties();
        /*
         * Set jcifs properties we know we want; soTimeout and cachePolicy to 30min.
         */
        p.setProperty("jcifs.smb.client.soTimeout", "1800000");
        p.setProperty("jcifs.netbios.cachePolicy", "1200");
        /*
         * The Filter can only work with NTLMv1 as it uses a man-in-the-middle

                    type: object
                    properties:
                      status:
                        type: string
                        example: green
                      timed_out:
                        type: boolean
                        example: false
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'

    }
}
```

## Configuration

### Basic Configuration Properties

```properties
# Connection settings
jcifs.smb.client.connTimeout=35000
jcifs.smb.client.soTimeout=180000
jcifs.smb.client.responseTimeout=30000

# Authentication
jcifs.smb.client.domain=WORKGROUP
jcifs.smb.client.username=guest
jcifs.smb.client.password=

# Protocol versions (SMB1 to SMB 3.1.1)

 * Permitted to short-circuit and not call `Chain.proceed()`.
 * Permitted to retry and make multiple calls to `Chain.proceed()`.
 * Can adjust Call timeouts using withConnectTimeout, withReadTimeout, withWriteTimeout.

**Network Interceptors**

 * Able to operate on intermediate responses like redirects and retries.