- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 5,539 for http (0.04 sec)
-
docs/es/docs/advanced/security/http-basic-auth.md
# HTTP Basic Auth Para los casos más simples, puedes usar HTTP Basic Auth. En HTTP Basic Auth, la aplicación espera un header que contiene un nombre de usuario y una contraseña. Si no lo recibe, devuelve un error HTTP 401 "Unauthorized". Y devuelve un header `WWW-Authenticate` con un valor de `Basic`, y un parámetro `realm` opcional. Eso le dice al navegador que muestre el prompt integrado para un nombre de usuario y contraseña.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 18:26:57 UTC 2024 - 5.1K bytes - Viewed (0) -
docs/en/docs/advanced/security/http-basic-auth.md
# HTTP Basic Auth { #http-basic-auth } For the simplest cases, you can use HTTP Basic Auth. In HTTP Basic Auth, the application expects a header that contains a username and a password. If it doesn't receive it, it returns an HTTP 401 "Unauthorized" error. And returns a header `WWW-Authenticate` with a value of `Basic`, and an optional `realm` parameter. That tells the browser to show the integrated prompt for a username and password.Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 5K bytes - Viewed (0) -
docs/ru/docs/deployment/https.md
Обычной практикой является иметь **одну программу/HTTP-сервер** запущенную на сервере (машине, хосте и т.д.) и **ответственную за всю работу с HTTPS**: * получение **зашифрованных HTTPS-запросов** * отправка **расшифрованных HTTP запросов** в соответствующее HTTP-приложение, работающее на том же сервере (в нашем случае, это приложение **FastAPI**) * получение **HTTP-ответа** от приложения
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 20.7K bytes - Viewed (0) -
docs/pt/docs/deployment/https.md
**protocolo HTTP**. É uma prática comum ter um **programa/servidor HTTP** em execução no servidor (máquina, host, etc.) e **gerenciar todas as partes HTTPS**: **recebendo as requisições encriptadas**, 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 HTTPS** apropriado e envie-a de volta ao cliente usando **HTTPS**. Este...
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 12.8K bytes - Viewed (0) -
docs/es/docs/deployment/https.md
con el **protocolo HTTP**. Es una práctica común tener **un programa/servidor HTTP** ejecutándose en el servidor (la máquina, host, etc.) y **gestionando todas las partes de HTTPS**: recibiendo los **requests HTTPS encriptados**, enviando los **requests HTTP desencriptados** a la aplicación HTTP real que se ejecuta en el mismo servidor (la aplicación **FastAPI**, en este caso), tomando el **response HTTP** de la aplicación, **encriptándolo** usando el **certificado HTTPS** adecuado y enviándolo...
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 13K 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 Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 19:34:08 UTC 2025 - 14.3K 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 Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 13.6K bytes - Viewed (0) -
docs/ja/docs/deployment/https.md
サーバー(マシン、ホストなど)上で**1つのプログラム/HTTPサーバー**を実行させ、**HTTPSに関する全てのこと**を管理するのが一般的です。 **暗号化された HTTPS リクエスト** を受信し、**復号化された HTTP リクエスト** を同じサーバーで実行されている実際の HTTP アプリケーション(この場合は **FastAPI** アプリケーション)に送信し、アプリケーションから **HTTP レスポンス** を受け取り、適切な **HTTPS 証明書** を使用して **暗号化** し、そして**HTTPS** を使用してクライアントに送り返します。
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 15.5K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http2/Http2.kt
* See the License for the specific language governing permissions and * limitations under the License. */ package okhttp3.internal.http2 import okhttp3.internal.format import okio.ByteString.Companion.encodeUtf8 object Http2 { @JvmField val CONNECTION_PREFACE = "PRI * HTTP/2.0\r\n\r\nSM\r\n\r\n".encodeUtf8() /** The initial max frame size, applied independently writing to, or reading from the peer. */Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 5.7K bytes - Viewed (0) -
okhttp/src/jvmTest/kotlin/okhttp3/HttpUrlTest.kt
assertThat(parse("http:\\/host/path")) .isEqualTo(parse("http://host/path")) assertThat(parse("http:/\\host/path")) .isEqualTo(parse("http://host/path")) assertThat(parse("http:\\\\host/path")) .isEqualTo(parse("http://host/path")) assertThat(parse("http:///host/path")) .isEqualTo(parse("http://host/path")) assertThat(parse("http:\\//host/path")) .isEqualTo(parse("http://host/path"))
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Mon Aug 04 07:38:48 UTC 2025 - 69.9K bytes - Viewed (0)