- Sort Score
- Result 10 results
- Languages All
Results 71 - 80 of 3,569 for httpx (0.07 sec)
-
docs/de/docs/alternatives.md
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Sun Oct 20 19:20:23 UTC 2024 - 26.7K bytes - Viewed (0) -
docs/en/docs/release-notes.md
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Sat Oct 26 16:51:17 UTC 2024 - 449.4K bytes - Viewed (0) -
docs/fr/docs/deployment/https.md
gérant toutes les parties HTTPS : envoyer les requêtes HTTP décryptées à l'application HTTP réelle fonctionnant sur
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 4.1K bytes - Viewed (0) -
docs/pt/docs/deployment/https.md
programa/servidor HTTP em execução no servidor (máquina, host, etc.) e gerenciar todas as partes HTTPS: enviando as solicitações HTTP descriptografadas para o aplicativo HTTP real em execução no mesmo servidor (a aplicação **FastAPI**, neste caso), pegue a resposta HTTP do aplicativo, criptografe-a usando o certificado apropriado e envie-a de volta ao cliente usando HTTPS. Este servidor é frequentemente chamado de <a href="https://en.wikipedia.org/wiki/TLS_termination_proxy" class="external-link" target="_blank">TLS...
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 3.9K bytes - Viewed (0) -
docs/en/docs/deployment/https.md
with the **HTTP protocol**. It is a common practice to have **one program/HTTP server** running on the server (the machine, host, etc.) and **managing all the HTTPS parts**: receiving the **encrypted HTTPS requests**, sending the **decrypted HTTP requests** to the actual HTTP application running in the same server (the **FastAPI** application, in this case), take the **HTTP response** from the application, **encrypt it** using the appropriate **HTTPS certificate** and sending it back to the...
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 12K bytes - Viewed (0) -
docs/ja/docs/deployment/https.md
サーバー(マシン、ホストなど)上で**1つのプログラム/HTTPサーバー**を実行させ、**HTTPSに関する全てのこと**を管理するのが一般的です。 **暗号化された HTTPS リクエスト** を受信し、**復号化された HTTP リクエスト** を同じサーバーで実行されている実際の HTTP アプリケーション(この場合は **FastAPI** アプリケーション)に送信し、アプリケーションから **HTTP レスポンス** を受け取り、適切な **HTTPS 証明書** を使用して **暗号化** し、そして**HTTPS** を使用してクライアントに送り返します。
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 15.4K bytes - Viewed (0) -
docs/ru/docs/deployment/https.md
Обычной практикой является иметь **одну программу/HTTP-сервер** запущенную на сервере (машине, хосте и т.д.) и **ответственную за всю работу с HTTPS**: * получение **зашифрованных HTTPS-запросов** * отправка **расшифрованных HTTP запросов** в соответствующее HTTP-приложение, работающее на том же сервере (в нашем случае, это приложение **FastAPI**) * получение **HTTP-ответа** от приложения
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 20.7K bytes - Viewed (0) -
docs/de/docs/deployment/https.md
* Die Inhalte sind **verschlüsselt**, auch wenn sie mit dem **HTTP-Protokoll** gesendet werden.
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 13.6K bytes - Viewed (0) -
docs/zh/docs/deployment/https.md
* SNI 扩展允许一台服务器(具有 **单个 IP 地址**)拥有 **多个 HTTPS 证书** 并提供 **多个 HTTPS 域名/应用程序**。 * 为此,服务器上会有**单独**的一个组件(程序)侦听**公共 IP 地址**,这个组件必须拥有服务器中的**所有 HTTPS 证书**。 * **获得安全连接后**,通信协议**仍然是HTTP**。 * 内容是 **加密过的**,即使它们是通过 **HTTP 协议** 发送的。
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Mon Aug 12 21:47:53 UTC 2024 - 10.7K bytes - Viewed (0) -
docs/en/docs/img/deployment/https/https.svg
https.svg...
Registered: Sun Oct 27 07:19:11 UTC 2024 - Last Modified: Thu May 12 00:06:16 UTC 2022 - 39.5K bytes - Viewed (0)