ntlmServlet.service(request, response);

            // When NtlmSsp.authenticate returns null, the service method returns early
            // without setting session attributes
            verify(session, never()).setAttribute(anyString(), any());
        }
    }

    /**

        // Test with cross-midnight rule
        IntervalRule crossRule = new IntervalRule("22:00", "02:00", "1", 1000); // Sunday only
        // For cross-midnight rule, when checking early morning hours (1:30), it checks day+1
        // day=8 becomes day=1, so day+1=2, which is Monday (not Sunday)
        assertFalse(crossRule.isTarget(1, 30, 8)); // Should be treated as day 1 (Sunday), checking day+1=2 (Monday)

        CIFSException ex = assertThrows(CIFSException.class, () -> ctx.initSecContext(new byte[] { firstByte }, 0, 1));
        assertEquals("Invalid token", ex.getMessage());

        // Ensure mechContext was not engaged due to early failure
        verify(this.mechContext, never()).initSecContext(any(), anyInt(), anyInt());
    }

    @Test
    @DisplayName("initSecContext with null buffer and non-zero len throws NPE")

also means that if something changed, it will be **reflected** on the client code automatically. And if you **build** the client, it will error out if you have any **mismatch** in the data used.

So, you would **detect many errors** very early in the development cycle instead of having to wait for the errors to show up to your final users in production and then trying to debug where the problem is. ✨...

 *  Upgrade: [Kotlin 1.8.21][kotlin_1_8_21].


## Version 4.11.0

_2023-04-22_

 *  Fix: Don't fail the call when the response code is ‘HTTP 102 Processing’ or
    ‘HTTP 103 Early Hints’.
 *  Fix: Read the response even if writing the request fails. This means you'll get a proper HTTP
    response even if the server rejects your request body.

    return (FluentFuture<V>) Futures.catchingAsync(this, exceptionType, fallback, executor);
  }

  /**
   * Returns a future that delegates to this future but will finish early (via a {@link
   * TimeoutException} wrapped in an {@link ExecutionException}) if the specified timeout expires.
   * If the timeout expires, not only will the output future finish, but also the input future

 *  Fix: Don't infinite loop when a received web socket message has self-terminating compressed
    data.

 *  Fix: Don't fail the call when the response code is ‘HTTP 102 Processing’ or ‘HTTP 103 Early
    Hints’.

 *  Fix: Honor interceptors' changes to connect and read timeouts.

 *  Fix: Recover gracefully when a cached response is corrupted on disk.

        statusLine.code == HTTP_CONTINUE -> {
          state = STATE_READ_RESPONSE_HEADERS
          responseBuilder
        }

        statusLine.code in (102 until 200) -> {
          // Processing and Early Hints will mean a second headers are coming.
          // Treat others the same for now
          state = STATE_READ_RESPONSE_HEADERS
          responseBuilder
        }

        else -> {

   - Create comprehensive test suite
   - Document API changes

3. **Community Engagement**:
   - Announce implementation plan
   - Solicit feedback from users
   - Identify beta testers for early access

## References

- [MS-SMB2]: Server Message Block (SMB) Protocol Version 2 and 3
- [MS-SWN]: Service Witness Protocol
- [MS-SMBD]: SMB2 Remote Direct Memory Access (RDMA) Transport Protocol

of cookies that net/http will accept when parsing HTTP headers. If the number of
cookie in a header exceeds the number set in `httpcookiemaxnum`, cookie parsing
will fail early. The default value is `httpcookiemaxnum=3000`. Setting
`httpcookiemaxnum=0` will allow the cookie parsing to accept an indefinite
number of cookies. To avoid denial of service attacks, this setting and default