Tudo que precisamos fazer é manipular a requisição dentro de um bloco `try`/`except`:

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[14,16] *}

Se uma exceção ocorrer, a instância `Request` ainda estará em escopo, então podemos ler e fazer uso do corpo da requisição ao lidar com o erro:

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[17:19] *}

      <version>14.1.1</version>
      <version>14.2.0</version>
      <version>14.3.0</version>
      <version>14.4.0</version>
      <version>14.5.0</version>
      <version>14.6.0</version>
      <version>14.6.1</version>
      <version>14.7.0</version>
      <version>14.8.0</version>
      <version>14.9.0</version>
      <version>14.10.0</version>
      <version>14.11.0</version>
      <version>14.12.0</version>

      <version>14.1.1</version>
      <version>14.2.0</version>
      <version>14.3.0</version>
      <version>14.4.0</version>
      <version>14.5.0</version>
      <version>14.6.0</version>
      <version>14.6.1</version>
      <version>14.7.0</version>
      <version>14.8.0</version>
      <version>14.9.0</version>
      <version>14.10.0</version>
      <version>14.11.0</version>
      <version>14.12.0</version>

하지만 이 예시도 여전히 유효하며, 내부 컴포넌트와 상호작용하는 방법을 보여줍니다.

///

같은 접근 방식을 사용해 예외 핸들러에서 요청 바디에 접근할 수도 있습니다.

필요한 것은 `try`/`except` 블록 안에서 요청을 처리하는 것뿐입니다:

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[14,16] *}

예외가 발생하더라도 `Request` 인스턴스는 여전히 스코프 안에 남아 있으므로, 오류를 처리할 때 요청 바디를 읽고 활용할 수 있습니다:

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[17:19] *}

    @CsvSource({
            // Positive cases (should be accepted)
            "1, 1, true", // ATTR_READONLY
            "2, 2, true", // ATTR_HIDDEN
            "4, 4, true", // ATTR_SYSTEM
            "16, 16, true", // ATTR_DIRECTORY
            "32, 32, true", // ATTR_ARCHIVE
            "3, 1, true", // READONLY | HIDDEN vs READONLY
            "3, 2, true", // READONLY | HIDDEN vs HIDDEN

Alles, was wir tun müssen, ist, den Request innerhalb eines `try`/`except`-Blocks zu handhaben:

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[14,16] *}

Wenn eine Exception auftritt, befindet sich die `Request`-Instanz weiterhin im Gültigkeitsbereich, sodass wir den Requestbody lesen und bei der Fehlerbehandlung verwenden können:

Il suffit de traiter la requête dans un bloc `try`/`except` :

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[14,16] *}

Si une exception se produit, l'instance de `Request` sera toujours dans la portée, ce qui nous permet de lire et d'utiliser le corps de la requête lors du traitement de l'erreur :

Todo lo que necesitamos hacer es manejar el request dentro de un bloque `try`/`except`:

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[14,16] *}

Si ocurre una excepción, la `Request instance` aún estará en el alcance, así que podemos leer y hacer uso del request body cuando manejamos el error:

We can also use this same approach to access the request body in an exception handler.

All we need to do is handle the request inside a `try`/`except` block:

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[14,16] *}

If an exception occurs, the`Request` instance will still be in scope, so we can read and make use of the request body when handling the error:

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[17:19] *}

但本範例仍然有效，並示範了如何與內部元件互動。

///

我們也可以用同樣的方法，在例外處理器中存取請求本文。

我們只需要在 `try`/`except` 區塊中處理請求即可：

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[14,16] *}

若發生例外，`Request` 實例依然在作用域內，因此在處理錯誤時我們仍可讀取並使用請求本文：

{* ../../docs_src/custom_request_and_route/tutorial002_an_py310.py hl[17:19] *}

## 在路由器中自訂 `APIRoute` 類別 { #custom-apiroute-class-in-a-router }