assertEquals("/site1/search", result.getRoutingPath());

        // The header remains for subsequent tests due to static request handling
        // Different matching header added to same request
        request.addHeader("X-Forwarded-Host", "test.com");
        result = virtualHostHelper.getVirtualHostPath(page);
        assertEquals("/site1/search", result.getRoutingPath()); // Still site1 due to header precedence

        void testValueConsistency() {
            // Given: Same input value
            int inputValue = 1000;
            int expectedMasked = inputValue & 0xFF; // 232

            // When: Creating multiple NdrShort instances
            NdrShort ndrShort1 = new NdrShort(inputValue);
            NdrShort ndrShort2 = new NdrShort(inputValue);

            // Then: All should have same masked value

For large responses, returning a `Response` directly is much faster than returning a dictionary.

This is because by default, FastAPI will inspect every item inside and make sure it is serializable as JSON, using the same [JSON Compatible Encoder](../tutorial/encoder.md){.internal-link target=_blank} explained in the tutorial. This is what allows you to return **arbitrary objects**, for example database models.

      val newSize = deflatedBytes.size - LAST_OCTETS_COUNT_TO_REMOVE_AFTER_DEFLATION
      deflatedBytes.readAndWriteUnsafe().use { cursor ->
        cursor.resizeBuffer(newSize)
      }
    } else {
      // Same as adding EMPTY_DEFLATE_BLOCK and then removing 4 bytes.
      deflatedBytes.writeByte(0x00)
    }

    buffer.write(deflatedBytes, deflatedBytes.size)
  }

  @Throws(IOException::class)

These examples are intentionally simple, but show how it all works.

In the chapters about security, there are utility functions that are implemented in this same way.

If you understood all this, you already know how those utility tools for security work underneath.

        assertNull(exception.getCause());
        assertTrue(exception.aborted());
    }

    public void test_aborted_multipleCallsReturnSameValue() {
        // Test that multiple calls to aborted() return the same value
        String url = "http://example.com/test";
        String message = "Test message";
        Exception cause = new RuntimeException("Test cause");
        boolean abort = true;

> Please note that losing the `MINIO_KMS_SECRET_KEY` will cause data loss
> since you will not be able to decrypt the IAM/configuration data anymore.
For distributed MinIO deployments, specify the *same* `MINIO_KMS_SECRET_KEY` for each MinIO server process.

At any point in time you can switch from `MINIO_KMS_SECRET_KEY` to a full KMS
deployment. You just need to import the generated key into KES - for example via

        assertTrue(reqCap.getValue() instanceof Smb2ChangeNotifyRequest);
    }

    // call() should delegate to watch() and return the same list
    @Test
    @DisplayName("call() delegates to watch() and returns same result")
    void call_delegatesToWatch() throws Exception {
        List<FileNotifyInformation> info = new ArrayList<>();
        NotifyResponse resp = mock(NotifyResponse.class);

64 sets, which is *16* 64 = 1024* drives in total.

- *If total number of nodes are of odd number then GCD algorithm provides affinity towards odd number erasure sets to provide for uniform distribution across nodes*. This is to ensure that same number of drives are pariticipating in any erasure set. For example if you have 2 nodes with 180 drives then GCD is 15 but this would lead to uneven distribution, one of the nodes would participate more drives. To avoid this the affinity is given towards...

    assertFalse(completed);
    thread.start();
    thread.join();
    assertTrue(completed);

    // Creating a new thread from the same ThreadFactory will have the same
    // pool ID but a thread ID of 2.
    Thread thread2 = threadFactory.newThread(monitoredRunnable);
    checkThreadPoolName(thread2, 2);
    assertEquals(