<img src="/img/deployment/https/https05.drawio.svg">

### HTTP-Response { #http-response }

Die Anwendung würde den Request verarbeiten und eine **einfache (unverschlüsselte) HTTP-Response** an den TLS-Terminierungsproxy senden.

<img src="/img/deployment/https/https06.drawio.svg">

### HTTPS-Response { #https-response }

Você vai com seu _crush_ na lanchonete, e fica na fila enquanto o caixa pega os pedidos das pessoas na sua frente. 😍

<img src="/img/async/concurrent-burgers/concurrent-burgers-01.png" class="illustration">

Então chega a sua vez, você pede dois saborosos hambúrgueres para você e seu _crush_.  🍔🍔

<img src="/img/async/concurrent-burgers/concurrent-burgers-02.png" class="illustration">

Die JSON-Schemas Ihrer Modelle werden Teil Ihres OpenAPI-generierten Schemas und in der interaktiven API-Dokumentation angezeigt:

<img src="/img/tutorial/body/image01.png">

Und werden auch in der API-Dokumentation innerhalb jeder *Pfadoperation*, die sie benötigt, verwendet:

<img src="/img/tutorial/body/image02.png">

## Editor-Unterstützung { #editor-support }

<img src="/img/tutorial/extending-openapi/image02.png">

Sie können sie jedoch deaktivieren, indem Sie `syntaxHighlight` auf `False` setzen:

{* ../../docs_src/configure_swagger_ui/tutorial001_py310.py hl[3] *}

... und dann zeigt die Swagger-Oberfläche die Syntaxhervorhebung nicht mehr an:

<img src="/img/tutorial/extending-openapi/image03.png">

      private val client = OkHttpClient()

      fun run() {
        // Use the imgur image upload API as documented at https://api.imgur.com/endpoints/image
        val requestBody = MultipartBody.Builder()
            .setType(MultipartBody.FORM)
            .addFormDataPart("title", "Square Logo")
            .addFormDataPart("image", "logo-square.png",
                File("docs/images/logo-square.png").asRequestBody(MEDIA_TYPE_PNG))

Os JSON Schemas dos seus modelos farão parte do esquema OpenAPI gerado para sua aplicação, e aparecerão na documentação interativa da API:

<img src="/img/tutorial/body/image01.png">

E também serão utilizados na documentação da API dentro de cada *operação de rota* que precisar deles:

<img src="/img/tutorial/body/image02.png">

## Suporte do editor { #editor-support }

  # The GCE defaults disable IPv4 forwarding, which breaks the Docker
  # build. Workaround this by renaming the file so that it is executed
  # earlier than our own overrides.
  #
  # This ultimately needs to be fixed at the image level - see infra
  # issue 15654.
  sudo mv /etc/sysctl.d/99-gce.conf /etc/sysctl.d/98-gce.conf
fi

# Required by bats
sudo touch /etc/is_vagrant_vm
sudo useradd vagrant

set -e

これでクライアントコードを import して利用できます。例えば次のようになり、メソッドに対して補完が効きます:

<img src="/img/tutorial/generate-clients/image02.png">

送信するペイロードにも補完が適用されます:

<img src="/img/tutorial/generate-clients/image03.png">

/// tip | 豆知識

FastAPI アプリの `Item` モデルで定義した `name` と `price` に補完が効いている点に注目してください。

///

送信データに対するインラインエラーも表示されます:

<img src="/img/tutorial/generate-clients/image04.png">

レスポンスオブジェクトにも補完があります:

因此，用戶端送出一個 **HTTPS 請求**。它其實就是透過加密的 TLS 連線發送的一個 HTTP 請求。

<img src="/img/deployment/https/https04.drawio.svg">

### 解密請求 { #decrypt-the-request }

TLS 終止代理會依照先前協商的方式**解密請求**，並將**純（已解密）的 HTTP 請求**轉交給運行應用的行程（例如以 Uvicorn 執行的 FastAPI 應用行程）。

<img src="/img/deployment/https/https05.drawio.svg">

### HTTP 回應 { #http-response }

應用會處理該請求，並將**純（未加密）的 HTTP 回應**送回 TLS 終止代理。

<img src="/img/deployment/https/https06.drawio.svg">

Directory for image cache....