mockHolder[0] = mock;
            return mock;
        });
        req.timeout(3000, 5000);
        // onConnect runs AFTER timeout, so it can override
        req.onConnect((r, conn) -> {
            conn.setReadTimeout(9999);
            onConnectReadTimeout.set(conn.getReadTimeout());
        });

        // ## Act ##

        // Setting onConnect to null should work
        request.onConnect(null);

        assertNotNull(request);
    }

    @Test
    public void testMultipleOnConnectCalls() {
        CurlRequest request = new CurlRequest(Method.GET, "https://example.com");

        // Multiple onConnect calls should work (last one wins)
        request.onConnect((req, conn) -> conn.setConnectTimeout(1000));

  }

  class DelayingSocketFactory(
    val onConnect: Socket.(timeout: Int) -> Unit = {},
    val onRead: Socket.() -> Unit = {},
    val onWrite: Socket.() -> Unit = {},
  ) : DelegatingSocketFactory(getDefault()) {
    override fun createSocket(): Socket {
      return object : Socket() {
        override fun connect(
          endpoint: SocketAddress?,
          timeout: Int,
        ) {

    /**
     * Sets the connection builder for customizing the connection.
     *
     * @param connectionBuilder the connection builder
     * @return this CurlRequest instance
     */
    public CurlRequest onConnect(final BiConsumer<CurlRequest, HttpURLConnection> connectionBuilder) {
        this.connectionBuilder = connectionBuilder;
        return this;
    }

    /**
     * Adds a request parameter.
     *

`data` e `raw_data` são mutuamente exclusivos. Você só pode definir um deles em cada `ServerSentEvent`.

///

## Retomando com `Last-Event-ID` { #resuming-with-last-event-id }

Quando um navegador se reconecta após uma queda na conexão, ele envia o último `id` recebido no cabeçalho `Last-Event-ID`.

Você pode lê-lo como um parâmetro de cabeçalho e usá-lo para retomar o stream de onde o cliente parou:

///

## OpenID Connect { #openid-connect }

OpenID Connect, **OAuth2** tabanlı başka bir spesifikasyondur.

OAuth2’de nispeten belirsiz kalan bazı noktaları tanımlayarak onu daha birlikte çalışabilir (interoperable) hâle getirmeye çalışır.

Örneğin, Google ile giriş OpenID Connect kullanır (arka planda OAuth2 kullanır).

    protected static final String OIC_REDIRECT_URL = "oic.redirect.url";

    /** Configuration key for OpenID Connect token server URL. */
    protected static final String OIC_TOKEN_SERVER_URL = "oic.token.server.url";

    /** Configuration key for OpenID Connect client secret. */
    protected static final String OIC_CLIENT_SECRET = "oic.client.secret";

///

## OpenID Connect { #openid-connect }

OpenID Connect 是另一个基于 **OAuth2** 的规范。

它只是扩展了 OAuth2，并明确了一些在 OAuth2 中相对模糊的内容，以尝试使其更具互操作性。

例如，Google 登录使用 OpenID Connect（底层使用OAuth2）。

但是 Facebook 登录不支持 OpenID Connect。它具有自己的 OAuth2 风格。

### OpenID（非「OpenID Connect」） { #openid-not-openid-connect }

还有一个「OpenID」规范。它试图解决与 **OpenID Connect** 相同的问题，但它不是基于 OAuth2。

因此，它是一个完整的附加系统。

///

## OpenID Connect { #openid-connect }

OpenID Connect — это ещё одна спецификация, основанная на **OAuth2**.

Она просто расширяет OAuth2, уточняя некоторые вещи, которые относительно неоднозначны в OAuth2, стараясь сделать его более совместимым.

Например, для входа в Google используется OpenID Connect (который под капотом использует OAuth2).

///

## OpenID Connect { #openid-connect }

OpenID Connect es otra especificación, basada en **OAuth2**.

Solo extiende OAuth2 especificando algunas cosas que son relativamente ambiguas en OAuth2, para intentar hacerla más interoperable.

Por ejemplo, el login de Google usa OpenID Connect (que internamente usa OAuth2).

Pero el login de Facebook no soporta OpenID Connect. Tiene su propia versión de OAuth2.