OkHttp URLConnection
====================

This module integrates OkHttp with `Authenticator` and `CookieHandler` from `java.net`.

This module is obsolete; prefer `okhttp-java-net-cookiejar`.

### Download

```kotlin
testImplementation("com.squareup.okhttp3:okhttp-urlconnection:5.3.0")

MockWebServer for JUnit 4
=========================

This module integrates mockwebserver3.MockWebServer with JUnit 4.

To use, first add this library as a test dependency:

```
testImplementation("com.squareup.okhttp3:mockwebserver3-junit4:5.3.0")
```

Then in tests annotated `@org.junit.Test`, you may declare a field with the `@Rule` annotation:

```
@Rule public final MockWebServerRule serverRule = new MockWebServerRule();
```

class APIKeyQuery(APIKeyBase):
    """
    API key authentication using a query parameter.

    This defines the name of the query parameter that should be provided in the request
    with the API key and integrates that into the OpenAPI documentation. It extracts
    the key value sent in the query parameter automatically and provides it as the
    dependency result. But it doesn't define how to send that API key to the client.

OkHttp java.net.CookieHandler
=============================

This module integrates OkHttp with `CookieHandler` from `java.net`.
This used to be part of `okhttp-urlconnection`

### Download

```kotlin
testImplementation("com.squareup.okhttp3:okhttp-java-net-cookiehandler:5.3.0")

MockWebServer for JUnit 5
=========================

This module integrates mockwebserver3.MockWebServer with JUnit 5.

To use, first add this library as a test dependency:

```
testImplementation("com.squareup.okhttp3:mockwebserver3-junit5:5.3.0")
```

Annotate fields in test classes with `@StartStop`. The server will be started and shut down
automatically.

```
class MyTest {

  @StartStop

---

### 🛠 **Seamless IDE & CI Integration**

Gradle is built to work smoothly with a variety of Integrated Development Environments (IDEs) and Continuous Integration (CI) systems, providing extensive support for a streamlined workflow:

track][tls_history] the dynamic TLS ecosystem and adjust OkHttp to improve connectivity and
security.

OkHttp uses your platform's built-in TLS implementation. On Java platforms OkHttp also supports
[Conscrypt][conscrypt], which integrates [BoringSSL](https://github.com/google/boringssl) with Java. OkHttp will use Conscrypt if it is
the first security provider:

```java
Security.insertProviderAt(Conscrypt.newProvider(), 1);
```

 * This class provides utilities for processing document content, titles, and digests,
 * handling text normalization, content extraction, and similar document hash encoding/decoding.
 * It also manages document processing requests and integrates with the crawler system.
 *
 */
public class DocumentHelper {
    private static final Logger logger = LogManager.getLogger(DocumentHelper.class);

    /** Prefix used for encoded similar document hashes */

 * thumbnail processing during indexing.
 *
 * <p>The IndexingHelper manages bulk operations, handles retries on failures,
 * and provides various query-based operations for document management.
 * It also integrates with the thumbnail generation system and handles
 * the cleanup of old documents during updates.</p>
 */
public class IndexingHelper {
    /** Logger for this class */

    HTTP/1.1. We also reimplemented our websocket client to use this new mechanism.

 *  New: The `okhttp-zstd` module negotiates [Zstandard (zstd)][zstd] compression with servers that
    support it. It integrates a new (unstable) [ZSTD-KMP] library, also from Square. Enable it like
    this:

    ```kotlin
    val client = OkHttpClient.Builder()
      .addInterceptor(CompressionInterceptor(Zstd, Gzip))
      .build()
    ```