bufferIndex += 12; // 10 reserved

        return bufferIndex - start;
    }

    @Override
    int readBytesWireFormat(final byte[] buffer, final int bufferIndex) {
        // handled special in SmbTransport.doRecv()
        return 0;
    }

    @Override
    public String toString() {

 * it as a {@code GwtIncompatible} annotation. And for {@code Futures.catching}, we need the GWT
 * compiler to autostrip the normal server method in order to expose the special, inherited GWT
 * version.
 */
@GwtCompatible
final class Partially {
  /**
   * The presence of this annotation on an API indicates that the method <i>may</i> be used with the

`Header` is a "sister" class of `Path`, `Query` and `Cookie`. It also inherits from the same common `Param` class.

But remember that when you import `Query`, `Path`, `Header`, and others from `fastapi`, those are actually functions that return special classes.

///

/// info

To declare headers, you need to use `Header`, because otherwise the parameters would be interpreted as query parameters.

///

## Automatic conversion { #automatic-conversion }

<div class="screenshot">
<img src="/img/tutorial/query-param-models/image01.png">
</div>

## Forbid Extra Query Parameters { #forbid-extra-query-parameters }

In some special use cases (probably not very common), you might want to **restrict** the query parameters that you want to receive.

You can use Pydantic's model configuration to `forbid` any `extra` fields:

You can verify it in the docs UI at `/docs`:

<div class="screenshot">
<img src="/img/tutorial/request-form-models/image01.png">
</div>

## Forbid Extra Form Fields { #forbid-extra-form-fields }

In some special use cases (probably not very common), you might want to **restrict** the form fields to only those declared in the Pydantic model. And **forbid** any **extra** fields.

/// note

    @Override
    public Set<Plugin> getPluginsBoundByDefaultToAllLifecycles(String packaging) {
        Set<Plugin> plugins;

        // NOTE: The upper-case packaging name is intentional, that's a special hinting mode used for certain tests
        if ("JAR".equals(packaging)) {
            plugins = new LinkedHashSet<>();

            plugins.add(newPlugin("maven-compiler-plugin", "compile", "testCompile"));

Historically, Gradle has shipped with some Groovy types in very prominent APIs.
This required the Kotlin DSL to add special integration to work with Groovy closures.
This has also forced plugins written in languages other than Groovy to use Groovy types for some APIs.

            when(mockReferral.getSpecialName()).thenReturn("\\SPECIAL");

            String reqPath = "\\\\domain\\root";
            long expire = System.currentTimeMillis() + 30000;
            int consumed = 10;

            DfsReferralDataImpl result = DfsReferralDataImpl.fromReferral(mockReferral, reqPath, expire, consumed);

            assertEquals("special", result.getServer());
        }

        @Test

        assertTrue(true, "Concurrent setFileId calls should complete without issues");
    }

    @Test
    @DisplayName("Should handle file ID with special patterns")
    void testSpecialFileIdPatterns() {
        // Test various special patterns
        byte[] allZeros = new byte[16];
        byte[] allOnes = new byte[16];
        Arrays.fill(allOnes, (byte) 0xFF);
        byte[] alternating = new byte[16];

        assertEquals((byte) 0x04, dst[2]); // Second buffer format byte
    }

    /**
     * Test writeBytesWireFormat with special characters in file names
     */
    @Test
    @DisplayName("Test writeBytesWireFormat with special characters in file names")
    public void testWriteBytesWireFormatSpecialCharacters() {
        // Given
        String oldFileName = "file with spaces.txt";