assertEquals(0, response.writeDataWireFormat(null, 0));

        // Read methods return 0 without accessing null buffer
        assertEquals(0, response.readSetupWireFormat(null, 0, 0));
        assertEquals(0, response.readParametersWireFormat(null, 0, 0));
        assertEquals(0, response.readDataWireFormat(null, 0, 0));
    }

    @Test

      val code = response.code
      if (code != HTTP_TEMP_REDIRECT && code != HTTP_PERM_REDIRECT) return response
      val method = response.request.method
      if (method == "GET" || method == "HEAD") return response
      val location = response.header("Location") ?: return response
      return response
        .newBuilder()
        .removeHeader("Location")
        .header("LegacyRedirectInterceptor-Location", location)

* Add support for declaring a `Response` parameter:
    * This allows declaring:
        * [Response Cookies](https://fastapi.tiangolo.com/advanced/response-cookies/).
        * [Response Headers](https://fastapi.tiangolo.com/advanced/response-headers/).
        * An HTTP Status Code different than the default: [Response - Change Status Code](https://fastapi.tiangolo.com/advanced/response-change-status-code/).

# `Response` class

You can declare a parameter in a *path operation function* or dependency to be of type `Response` and then you can set data for the response like headers or cookies.

You can also use it directly to create an instance of it and return it from your *path operations*.

Read more about it in the [FastAPI docs about returning a custom Response](https://fastapi.tiangolo.com/advanced/response-directly/#returning-a-custom-response)

package org.codelibs.fess.suggest.request;

/**
 * The Response interface serves as a marker interface for all response types
 * in the suggestion system. Implementations of this interface are used to
 * encapsulate the results of various operations and queries within the system.
 *
 * <p>Classes implementing this interface should provide specific details and
 * data relevant to the type of response they represent.</p>
 */
public interface Response {

        int result2 = response2.readDataWireFormat(buffer, 20, sourceData.length);
        assertEquals(sourceData.length, result2);

        // Test with offset near end
        byte[] outputBuffer3 = new byte[1024];
        TransCallNamedPipeResponse response3 = new TransCallNamedPipeResponse(mockConfig, outputBuffer3);
        System.arraycopy(sourceData, 0, buffer, 45, sourceData.length);

    server.enqueue(MockResponse(body = "response that will never be received"))
    val response = executeSynchronously("/")
    response.assertFailure(
      // JDK 11 response to the FAIL_HANDSHAKE:
      SSLException::class.java,
      // RI response to the FAIL_HANDSHAKE:
      SSLProtocolException::class.java,
      // Android's response to the FAIL_HANDSHAKE:
      SSLHandshakeException::class.java,

{* ../../docs_src/response_model/tutorial003_02_py310.py hl[8,10:11] *}

このシンプルなケースは、戻り値の型アノテーションが `Response` のクラス（またはサブクラス）であるため、FastAPIが自動的に処理します。

また `RedirectResponse` と `JSONResponse` の両方は `Response` のサブクラスなので、ツールも型アノテーションが正しいとして問題にしません。

### `Response`のサブクラスをアノテーションする { #annotate-a-response-subclass }

型アノテーションで `Response` のサブクラスを使うこともできます:

<img src="/img/tutorial/response-model/image01.png">

而且兩個模型都會用在互動式 API 文件中：

<img src="/img/tutorial/response-model/image02.png">

## 其他回傳型別註解 { #other-return-type-annotations }

有時你回傳的東西不是有效的 Pydantic 欄位，你仍會在函式上加上註解，只為了獲得工具（編輯器、mypy 等）提供的支援。

### 直接回傳 Response { #return-a-response-directly }

最常見的情況是[直接回傳 Response（在進階文件中稍後會解釋）](../advanced/response-directly.md)。

            // When & Then
            assertEquals(0, response.writeBytesWireFormat(dst, 0));
            assertEquals(0, response.writeBytesWireFormat(dst, 25));
            assertEquals(0, response.writeBytesWireFormat(dst, 50));
            assertEquals(0, response.writeBytesWireFormat(dst, 75));
            assertEquals(0, response.writeBytesWireFormat(dst, 99));
        }

        @Test