* Returns a view of the given byte array as a {@link ByteSource}. To view only a specific range
   * in the array, use {@code ByteSource.wrap(b).slice(offset, length)}.
   *
   * <p>Note that the given byte array may be passed directly to methods on, for example, {@code
   * OutputStream} (when {@code copyTo(OutputStream)} is called on the resulting {@code
   * ByteSource}). This could allow a malicious {@code OutputStream} implementation to modify the

FastAPI 會使用那個暫時性的回應來擷取標頭（還有 Cookie 與狀態碼），並把它們放到最終回應中；最終回應包含你回傳的值，且會依任何 `response_model` 進行過濾。

你也可以在依賴中宣告 `Response` 參數，並在其中設定標頭（與 Cookie）。

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

當你直接回傳 `Response` 時，也能加入標頭。

依照[直接回傳 Response](response-directly.md)中的說明建立回應，並把標頭作為額外參數傳入：

{* ../../docs_src/response_headers/tutorial001_py310.py hl[10:12] *}

/// note | 技術細節

    private rpc.sid_t mockSidT;

    @Mock
    private rpc.unicode_string mockUnicodeString;

    @Mock
    private lsarpc.LsarSidArray mockLsarSidArray;

    @BeforeEach
    void setUp() {
        // Directly set the deferred field on the mock
        mockNdrBuffer.deferred = mockDeferredBuffer;

        // Configure mocks for NdrBuffer interactions

`Response` パラメータは依存関係でも宣言でき、そこで Cookie（やヘッダー）を設定することも可能です。

## `Response` を直接返す { #return-a-response-directly }

コードで `Response` を直接返すときに、Cookie を作成することもできます。

そのためには、[Response を直接返す](response-directly.md) で説明されているとおりにレスポンスを作成します。

そのレスポンスに Cookie を設定してから返します:

{* ../../docs_src/response_cookies/tutorial001_py310.py hl[10:12] *}

/// tip | 豆知識

   *   <li>Use mmap(2) or equivalent. Requires that either the input channel or the output channel
   *       have file descriptors. Bytes are copied from the file into a kernel buffer, then directly
   *       into the other buffer (userspace). Note that if the file is very large, a naive
   *       implementation will effectively put the whole file in memory. On many systems with paging

    return new Builder<Comparable>(Ordering.natural()).maximumSize(maximumSize);
  }

  /**
   * The builder class used in creation of min-max priority queues. Instead of constructing one
   * directly, use {@link MinMaxPriorityQueue#orderedBy(Comparator)}, {@link
   * MinMaxPriorityQueue#expectedSize(int)} or {@link MinMaxPriorityQueue#maximumSize(int)}.
   *

absl::Status LoadDynamicLibrary(const char* library_filename, void** result,
                                const void** buf, size_t* len);

// TODO(josh11b,mrry): Change Session to be able to use a Graph*
// directly, instead of requiring us to serialize to a GraphDef and
// call Session::Extend().
bool ExtendSessionGraphHelper(TF_Session* session, TF_Status* status) {
  if (session->graph != nullptr) {

또한, 종속성에서 `Response` 매개변수를 선언하고 그 안에서 헤더(및 쿠키)를 설정할 수 있습니다.

## `Response` 직접 반환하기 { #return-a-response-directly }

`Response`를 직접 반환할 때에도 헤더를 추가할 수 있습니다.

[응답을 직접 반환하기](response-directly.md)에 설명한 대로 응답을 생성하고, 헤더를 추가 매개변수로 전달하세요:

{* ../../docs_src/response_headers/tutorial001_py310.py hl[10:12] *}

/// note | 기술 세부사항

    }

    /*
     * Some operating systems may return zero as the length for files denoting system-dependent
     * entities such as devices or pipes, in which case we must fall back on comparing the bytes
     * directly.
     */
    long len1 = file1.length();
    long len2 = file2.length();
    if (len1 != 0 && len2 != 0 && len1 != len2) {
      return false;
    }

    * It's mainly syntax sugar, a convenience for developer experience.
    * Now `Request`, `Response`, `WebSocket`, `status` can be imported directly from `fastapi` as in `from fastapi import Response`. This is because those are frequently used, to use the request directly, to set headers and cookies, to get status codes, etc.
    * Documentation changes in many places, but new docs and noticeable improvements: