The API Server will no longer proxy non-101 responses for upgrade requests. This could break proxied backends (such as an extension API server) that respond to upgrade requests with a non-101 response code. ([#92941](https://github.com/kubernetes/kubernetes/pull/92941), [@tallclair](https://github.com/tallclair)) [SIG API Machinery]
 
## Changes by Kind

<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)。

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

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

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

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

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

E as ferramentas também ficarão felizes porque `RedirectResponse` e ​​`JSONResponse` são subclasses de `Response`, então a anotação de tipo está correta.

### Anote uma subclasse de Response { #annotate-a-response-subclass }

Você também pode usar uma subclasse de `Response` na anotação de tipo:

    }

    String response2Body;
    try (Response response2 = client.newCall(request).execute()) {
      if (!response2.isSuccessful()) throw new IOException("Unexpected code " + response2);

      response2Body = response2.body().string();
      System.out.println("Response 2 response:          " + response2);
      System.out.println("Response 2 cache response:    " + response2.cacheResponse());

  The API Server will no longer proxy non-101 responses for upgrade requests. This could break proxied backends (such as an extension API server) that respond to upgrade requests with a non-101 response code. ([#92941](https://github.com/kubernetes/kubernetes/pull/92941), [@tallclair](https://github.com/tallclair)) [SIG API Machinery]

            response.readBytesWireFormat(buffer1, 0);
            assertEquals(1024, response.getCount());
            assertEquals(512, response.getRemaining());

            // Second read - should update values
            byte[] buffer2 = createValidWriteResponse(2048, 1024);
            response.readBytesWireFormat(buffer2, 0);
            assertEquals(2048, response.getCount());

* The `emptyDir.sizeLimit` field is now correctly omitted from API requests and responses when unset. ([#50163](https://github.com/kubernetes/kubernetes/pull/50163), [@jingxu97](https://github.com/jingxu97))

    public void test_constructorWithoutErrors() throws Exception {
        SuggestDeleteResponse response = new SuggestDeleteResponse(null, 100);

        assertNotNull(response);
        assertEquals(100, response.getTook());
        assertFalse(response.hasError());
        assertNotNull(response.getErrors());
        assertEquals(0, response.getErrors().size());
    }

    @Test

# Código de status de resposta { #response-status-code }

Da mesma forma que você pode especificar um modelo de resposta, você também pode declarar o código de status HTTP usado para a resposta com o parâmetro `status_code` em qualquer uma das *operações de rota*:

* `@app.get()`
* `@app.post()`
* `@app.put()`
* `@app.delete()`
* etc.

{* ../../docs_src/response_status_code/tutorial001_py310.py hl[6] *}

/// note | Nota