OkHttpClient client = new OkHttpClient.Builder()
    .sslSocketFactory(clientCertificates.sslSocketFactory(), clientCertificates.trustManager())
    .build();
```

Client Authentication
---------------------

The above scenario is representative of most TLS set ups: the client uses certificates to validate
the identity of a server. The converse is also possible. Here we create a server that authenticates
a client and a client that authenticates a server.

	ProxyRequest                        bool      // only set for GET/HEAD in active-active replication scenario
	ProxyHeaderSet                      bool      // only set for GET/HEAD in active-active replication scenario
	ReplicationRequest                  bool      // true only if replication request
	ReplicationSourceTaggingTimestamp   time.Time // set if MinIOSourceTaggingTimestamp received

            return filtered;
        }

        // Distinct the projects to avoid duplicates.  Duplicates are possible in multi-module projects.
        //
        // Given a scenario where there is an aggregate POM with modules A, B, C, D, and E and project E depends on
        // A, B, C, and D. If the aggregate POM is being filtered for non-transitive and downstream dependencies where

### OpenAPI-Unterstützung { #openapi-support }

OpenAPI bietet nicht die Möglichkeit, dass ein *Pfad-Parameter* seinerseits einen *Pfad* enthalten kann, das würde zu Szenarios führen, die schwierig zu testen und zu definieren sind.

Trotzdem können Sie das in **FastAPI** tun, indem Sie eines der internen Tools von Starlette verwenden.

        // Act
        SmbSession result = handle.getSession();

        // Assert
        assertNull(result);
        verify(handle).getSession();
    }

    @Test
    @DisplayName("Scenario: verify interaction order across multiple calls")
    void verifyInteractionOrder() throws Exception {
        // Arrange: stub simple returns
        when(handle.hasCapability(anyInt())).thenReturn(true);

        assertEquals(firstCall, secondCall);
        assertEquals(secondCall, thirdCall);
    }

    // Test with changing query string (though typically wouldn't change in real scenario)
    @Test
    public void test_getServletPath_withChangingQueryString() {
        final String originalPath = "/original/path";
        final String customPath = "/api/v1/dynamic";

 * of the daemon and worker project that depends on it. Since both a daemon and worker
 * project depend on this library, that library must also be able to run in the
 * daemon and the worker.
 *
 * In this scenario, both the daemon and the worker project declare required target
 * runtimes. All projects that these two projects depend on will inherit these runtimes
 * as part of their computed target runtimes.
 *

                protected SmbResource adapt(FileEntry e) {
                    return resource;
                }
            };
        });
    }

    @Test
    @DisplayName("Complex scenario with multiple filter conditions")
    void complexFilterScenario() throws Exception {
        // Setup: three entries with different filter results
        FileEntry entry1 = mock(FileEntry.class);

## CSRF-Risiko { #csrf-risk }

Dieses Standardverhalten schützt vor einer Klasse von **Cross-Site Request Forgery (CSRF)**-Angriffen in einem sehr spezifischen Szenario.

Diese Angriffe nutzen aus, dass Browser Skripte Requests senden lassen, ohne einen CORS-Preflight-Check durchzuführen, wenn sie:

* keinen `Content-Type`-Header haben (z. B. mit `fetch()` und einem `Blob`-Body)

        assertNotNull(retrieved);
        assertEquals(engine, retrieved);
    }

    // Test concurrent-like scenario (sequential but simulating concurrent behavior)
    @Test
    public void test_add_multipleSameNameSequential() {
        TestScriptEngine engine1 = new TestScriptEngine("v1");