/**
   * The HTTP <a href="https://datatracker.ietf.org/doc/html/rfc6455">{@code
   * Sec-WebSocket-Protocol}</a> header field name.
   *
   * @since 28.0
   */
  public static final String SEC_WEBSOCKET_PROTOCOL = "Sec-WebSocket-Protocol";

  /**
   * The HTTP <a href="https://datatracker.ietf.org/doc/html/rfc6455">{@code
   * Sec-WebSocket-Version}</a> header field name.

    private final String targetHost;

    private byte[] preauthIntegrityHash;

    // Multi-channel support
    private ChannelManager channelManager;

    // Witness protocol support fields
    private WitnessClient witnessClient;
    private boolean witnessEnabled;

    // SMB3 lease support
    private LeaseManager leaseManager;

    // SMB3 persistent handle support

Ces en‑têtes conservent des informations sur la requête d'origine qui seraient autrement perdues :

* **X-Forwarded-For** : l'adresse IP du client d'origine
* **X-Forwarded-Proto** : le protocole d'origine (`https`)
* **X-Forwarded-Host** : l'hôte d'origine (`mysuperapp.com`)

Esses headers preservam informações sobre a requisição original que, de outra forma, seriam perdidas:

* **X-Forwarded-For**: o endereço IP original do cliente
* **X-Forwarded-Proto**: o protocolo original (`https`)
* **X-Forwarded-Host**: o host original (`mysuperapp.com`)

import jakarta.servlet.http.HttpServletResponse;
import jakarta.servlet.http.HttpSession;

/**
 * Authenticator for SAML 2.0.
 *
 * <p>This authenticator enables Single Sign-On (SSO) using SAML 2.0 protocol
 * with Identity Providers such as Okta, Azure AD, OneLogin, etc.</p>
 *
 * <h2>Required Configuration</h2>
 * <p>Add the following properties to {@code system.properties}:</p>
 * <pre>
 * # Enable SAML SSO

But it provides you the tools to simplify the process as much as possible without compromising flexibility, robustness, or security.

And you can use and implement secure, standard protocols, like OAuth2 in a relatively simple way.

   * A simple immutable data class to encapsulate the information to be found in a Teredo address.
   *
   * <p>All of the fields in this class are encoded in various portions of the IPv6 address as part
   * of the protocol. More protocols details can be found at: <a target="_parent"
   * href="http://en.wikipedia.org/wiki/Teredo_tunneling">http://en.wikipedia.
   * org/wiki/Teredo_tunneling</a>.
   *

            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-main" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-messaging" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-protocol" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-server" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-services" />

        @Test
        @DisplayName("Should handle negative values in buffer")
        void shouldHandleNegativeValuesInBuffer() throws SMBProtocolDecodingException {
            // Given - negative values (treated as unsigned in protocol)
            ByteBuffer buffer = ByteBuffer.allocate(24);
            buffer.order(ByteOrder.LITTLE_ENDIAN);
            buffer.putLong(-1L);
            buffer.putLong(-1L);
            buffer.putInt(-1);

Persistent handles (also known as durable handles) allow SMB3 connections to survive network disconnections, server reboots, and client reconnections. This feature is critical for enterprise reliability and seamless failover scenarios.

## 2. Protocol Specification Reference

- **MS-SMB2 Section 2.2.13.2.3**: SMB2_CREATE_DURABLE_HANDLE_REQUEST
- **MS-SMB2 Section 2.2.13.2.4**: SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2