* Set to -1 to disable automatic purging of user information.
     */
    @Min(-1)
    @Max(100000)
    @ValidateTypeFailure
    public Integer purgeUserInfoDay;

    /**
     * Bot user agents whose search logs should be purged.
     * Search logs from these bots will be automatically removed.
     */
    @Size(max = 10000)
    public String purgeByBots;

    /**

* Websockets - [RFC 6455](https://datatracker.ietf.org/doc/html/rfc6455)
* SSE - [Server-sent events](https://html.spec.whatwg.org/multipage/server-sent-events.html#server-sent-events)

Where the spec is ambiguous, OkHttp follows modern user agents such as popular Browsers or common HTTP Libraries.

OkHttp is principled and avoids being overly configurable, especially when such configuration is

# CoreOS stuff
/cluster/libvirt-coreos/coreos_*.img

# Downloaded Kubernetes binary release
/kubernetes/

# direnv .envrc files
.envrc

# Local agent override file
AGENTS.override.md
# TODO: remove once there is a merged AGENTS.md
AGENTS.md

# Downloaded kubernetes binary release tar ball
kubernetes.tar.gz

# Phony test files used as part of coverage generation
zz_generated_*_test.go

 *  Fix: Include a backwards-compatible `OkHttp-Response-Source` header with
    `OkUrlFactory `responses.
 *  Fix: Don't include a default User-Agent header in requests made with the Call
    API. Requests made with OkUrlFactory will continue to have a default user
    agent.
 *  New: Guava-like API to create headers:

    ```java
    Headers headers = Headers.of(name1, value1, name2, value2, ...).
    ```

    // ============================================================
    // User Agent Configuration
    // ============================================================

    /** Prefix for Fess crawler user agent string. */
    public static final String CRAWLING_USER_AGENT_PREFIX = "Mozilla/5.0 (compatible; Fess/";

    /** Suffix for Fess crawler user agent string with bot information URL. */

Imagina que construyes una forma de ejecutar un agente de IA local.

Provee un API en

```
http://localhost:8000/v1/agents/multivac
```

También hay un frontend en

```
http://localhost:8000
```

/// tip | Consejo

Ten en cuenta que ambos tienen el mismo host.

///

Luego, usando el frontend, puedes hacer que el agente de IA haga cosas en tu nombre.

	switch err.HTTPStatusCode {
	case http.StatusServiceUnavailable, http.StatusTooManyRequests:
		// Set retry-after header to indicate user-agents to retry request after 60 seconds.
		// https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After
		w.Header().Set(xhttp.RetryAfter, "60")
	}

	switch err.Code {
	case "InvalidRegion":

Yerelde çalışan bir AI agent’ı (yapay zeka ajanı) çalıştırmanın bir yolunu geliştirdiğinizi düşünün.

Bir API sunuyor:

```
http://localhost:8000/v1/agents/multivac
```

Ayrıca bir frontend var:

```
http://localhost:8000
```

/// tip | İpucu

İkisinin de host’u aynıdır.

///

Frontend’i kullanarak AI agent’a sizin adınıza işler yaptırabiliyorsunuz.

Imagine que você desenvolve uma forma de executar um agente de IA local.

Ele fornece uma API em

```
http://localhost:8000/v1/agents/multivac
```

Há também um frontend em

```
http://localhost:8000
```

/// tip | Dica

Observe que ambos têm o mesmo host.

///

Usando o frontend, você pode fazer o agente de IA executar ações em seu nome.

## Пример атаки { #example-attack }

Представьте, что вы сделали способ запускать локального ИИ-агента.

Он предоставляет API по адресу

```
http://localhost:8000/v1/agents/multivac
```

Есть также фронтенд по адресу

```
http://localhost:8000
```

/// tip | Совет

Обратите внимание, что у обоих один и тот же хост.

///