verify(response, never()).addHeader(eq("WWW-Authenticate"), eq("Basic realm=\"TestRealm\""));
    }

    @Test
    void testDoFilter_ntlmType1Message() throws Exception {
        // Test NTLM Type 1 message handling
        // This test verifies that when a Type 1 NTLM message is received,
        // the filter processes it correctly through NtlmSsp.authenticate

///

## ユースケース { #use-cases }

ユースケースの例:

* JSON ではないリクエストボディを JSON に変換する（例: [`msgpack`](https://msgpack.org/index.html)）。
* gzip 圧縮されたリクエストボディの解凍。
* すべてのリクエストボディの自動ロギング。

## カスタムリクエストボディのエンコーディングの処理 { #handling-custom-request-body-encodings }

gzip のリクエストを解凍するために、カスタムの `Request` サブクラスを使う方法を見ていきます。

そして、そのカスタムリクエストクラスを使うための `APIRoute` サブクラスを用意します。

### カスタム `GzipRequest` クラスの作成 { #create-a-custom-gziprequest-class }

    }

    /**
     * Creates a synonym item from the provided form data with validation.
     *
     * @param form the create form containing synonym data
     * @param hook the validation error hook for handling errors
     * @return OptionalEntity containing the created synonym item or empty if creation failed
     */
    protected OptionalEntity<SynonymItem> createSynonymItem(final CreateForm form, final VaErrorHook hook) {

            len += pad8(bufferIndex);
        } else if (compound && this.nextCommand == 0 && this.readSize > 0) {
            // Apply compound response handling as per MS-SMB2 3.2.5.1.9 - correct for both compound and single responses
            // 3.2.5.1.9 Handling Compounded Responses
            // The final response in the compounded response chain will have NextCommand equal to 0,

        concreteResponse.received();
        assertTrue(concreteResponse.isReceived());
        concreteResponse.clearReceived();
        assertFalse(concreteResponse.isReceived());

        // Test error handling
        assertFalse(concreteResponse.isError());
        assertEquals(0, concreteResponse.getErrorCode());
        concreteResponse.error();
        assertTrue(concreteResponse.isError());

/**
 * Tests for SmbFilenameFilter interface behaviors via simple implementations.
 * Each test creates a concrete filter to validate expected contract semantics
 * including normal operation, null handling, edge cases, and exception flow.
 */
@ExtendWith(MockitoExtension.class)
class SmbFilenameFilterTest {

    @Mock
    SmbFile mockDir;

    /**
     * Happy-path: a filter that accepts any name.
     */

///

Com isso você pode conectar o WebSocket e então enviar e receber mensagens:

<img src="/img/tutorial/websockets/image05.png">

## Lidando com desconexões e múltiplos clientes { #handling-disconnections-and-multiple-clients }

Quando uma conexão WebSocket é fechada, o `await websocket.receive_text()` levantará uma exceção `WebSocketDisconnect`, que você pode então capturar e lidar como neste exemplo.

   *       available even under older version.
   *   <li>Any property may be cleared through APIs like {@link System#clearProperty}.
   *   <li>Unusual environments like GWT may have their own special handling of system properties.
   * </ul>
   *
   * <p>Note that {@code StandardSystemProperty} does not provide constants for more recently added
   * properties, including:
   *
   * <ul>

    /**
     * Get the transport pool for managing SMB connections
     *
     * @return the transport pool
     */
    SmbTransportPool getTransportPool();

    /**
     * Get the DFS resolver for handling distributed file system paths
     *
     * @return the DFS instance for this context
     */
    DfsResolver getDfs();

    /**
     * Get the SID resolver for resolving security identifiers
     *

import java.util.Map;
import java.util.StringTokenizer;

/**
 * A <code>URLStreamHandler</code> used to provide NTLM authentication
 * capabilities to the default HTTP handler.  This acts as a wrapper,
 * handling authentication and passing control to the underlying
 * stream handler.
 */
public class Handler extends URLStreamHandler {

    /**
     * The default HTTP port (<code>80</code>).
     */