///

`GzipRequest.get_route_handler` が返す関数が異なるのは、`Request` を `GzipRequest` に変換する点だけです。

これにより、`GzipRequest` は必要に応じてデータを解凍してから *path operations* に渡します。

それ以降の処理ロジックはすべて同じです。

ただし、`GzipRequest.body` を変更しているため、必要に応じて **FastAPI** によって読み込まれる際にリクエストボディが自動的に解凍されます。

## 例外ハンドラでのリクエストボディへのアクセス { #accessing-the-request-body-in-an-exception-handler }

Mas, você já sabe como criar facilmente documentação automática para uma API com o **FastAPI**.

Então vamos usar esse mesmo conhecimento para documentar como a *API externa* deveria ser... criando as *operações de rota* que a *API externa* deveria implementar (as que sua API irá chamar).

/// tip | Dica

     *
     * @return the nativeFileSystem
     */
    public final String getNativeFileSystem() {
        return this.nativeFileSystem;
    }

    /**
     * Indicates whether the share supports search operations with search bits.
     *
     * @return the supportSearchBits
     */
    public final boolean isSupportSearchBits() {
        return this.supportSearchBits;
    }

    /**
     * @return the shareIsInDfs

        long decoded = Encdec.dec_uint32le(buffer, 0);

        // Then
        assertEquals(value & 0xFFFFFFFFL, decoded);
    }

    @Test
    @DisplayName("Should encode and decode strings using byte operations")
    void testStringOperations() {
        // Given
        String testString = "Hello";
        byte[] buffer = new byte[testString.length()];

        // When - Manual string encoding using individual bytes

import jcifs.internal.smb2.ioctl.SrvCopychunkCopy;
import jcifs.internal.smb2.ioctl.SrvRequestResumeKeyResponse;

/**
 * Utility class for SMB file copy operations.
 * Provides methods for efficient server-side copying using SMB2 IOCTL operations.
 *
 * @author mbechler
 *
 */
public final class SmbCopyUtil {

    private static final Logger log = LoggerFactory.getLogger(SmbCopyUtil.class);

    /**

 */

package jcifs.smb1.smb1;

/**
 * Interface defining NT status codes used in SMB1 protocol operations.
 * These status codes are returned by SMB servers to indicate the result
 * of requested operations. The codes follow the Windows NT status code format.
 */
public interface NtStatus {

    /* Don't bother to edit this. Everthing within the interface

    /**
     * Default constructor.
     */
    public ChatAction() {
        // Default constructor
    }

    /** The chat client for handling chat operations. */
    @Resource
    protected ChatClient chatClient;

    /** The session manager for managing chat sessions. */
    @Resource
    protected ChatSessionManager chatSessionManager;

    /**

 * governing permissions and limitations under the License.
 */
package org.codelibs.core.lang;

import java.util.function.LongSupplier;

/**
 * Utility class for system operations.
 *
 * @author wyukawa
 * @author shinsuke
 *
 */
public abstract class SystemUtil {

    /**
     * Do not instantiate.
     */
    protected SystemUtil() {
    }

    /**

 */
package jcifs.smb;

import java.io.IOException;

import jcifs.CIFSException;
import jcifs.SmbFileHandle;
import jcifs.SmbPipeHandle;

/**
 * Internal interface for SMB pipe handle operations.
 *
 * This interface extends SmbPipeHandle with additional methods needed
 * for internal pipe management and provides access to low-level pipe details.
 *
 * @author mbechler
 *

Si vas a la **UI de la documentación de la API** en `/docs` podrás ver la **documentación** de las cookies para tus *path operations*.

Pero incluso si **rellenas los datos** y haces clic en "Execute", como la UI de la documentación funciona con **JavaScript**, las cookies no serán enviadas y verás un **mensaje de error** como si no hubieras escrito ningún valor.