- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 100 for _proxy_ (0.04 sec)
-
docs/pt/docs/advanced/behind-a-proxy.md
Como temos um proxy com um prefixo de caminho de `/api/v1` para nossa aplicação, o frontend precisa buscar o OpenAPI schema em `/api/v1/openapi.json`. ```mermaid graph LR browser("Browser") proxy["Proxy on http://0.0.0.0:9999/api/v1/app"] server["Server on http://127.0.0.1:8000/app"] browser --> proxy proxy --> server ``` /// tip | Dica
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Nov 09 16:39:20 UTC 2024 - 12.2K bytes - Viewed (0) -
docs/es/docs/advanced/behind-a-proxy.md
Porque tenemos un proxy con un prefijo de path de `/api/v1` para nuestra aplicación, el frontend necesita obtener el esquema de OpenAPI en `/api/v1/openapi.json`. ```mermaid graph LR browser("Navegador") proxy["Proxy en http://0.0.0.0:9999/api/v1/app"] server["Servidor en http://127.0.0.1:8000/app"] browser --> proxy proxy --> server ``` /// tip | Consejo
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 18:26:57 UTC 2024 - 12.1K bytes - Viewed (0) -
docs/de/docs/advanced/behind-a-proxy.md
Da wir für unsere Anwendung einen Proxy mit dem Pfadpräfix `/api/v1` haben, muss das Frontend das OpenAPI-Schema unter `/api/v1/openapi.json` abrufen. ```mermaid graph LR browser("Browser") proxy["Proxy auf http://0.0.0.0:9999/api/v1/app"] server["Server auf http://127.0.0.1:8000/app"] browser --> proxy proxy --> server ``` /// tip | Tipp
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 13K bytes - Viewed (0) -
docs/en/docs/advanced/behind-a-proxy.md
# Behind a Proxy { #behind-a-proxy } In many situations, you would use a **proxy** like Traefik or Nginx in front of your FastAPI app. These proxies could handle HTTPS certificates and other things. ## Proxy Forwarded Headers { #proxy-forwarded-headers }
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 19:34:08 UTC 2025 - 16K bytes - Viewed (0) -
okhttp/src/jvmTest/kotlin/okhttp3/internal/connection/RouteSelectorTest.kt
private const val PROXY_A_HOST = "proxya" private val proxyA = Proxy( Proxy.Type.HTTP, InetSocketAddress.createUnresolved(PROXY_A_HOST, PROXY_A_PORT), ) private const val PROXY_B_PORT = 1002 private const val PROXY_B_HOST = "proxyb" private val proxyB = Proxy( Proxy.Type.HTTP,
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Fri May 30 21:28:20 UTC 2025 - 20.7K bytes - Viewed (0) -
docs/em/docs/advanced/behind-a-proxy.md
↩️ 👥 ✔️ 🗳 ⏮️ ➡ 🔡 `/api/v1` 👆 📱, 🕸 💪 ☕ 🗄 🔗 `/api/v1/openapi.json`. ```mermaid graph LR browser("Browser") proxy["Proxy on http://0.0.0.0:9999/api/v1/app"] server["Server on http://127.0.0.1:8000/app"] browser --> proxy proxy --> server ``` /// tip 📢 `0.0.0.0` 🛎 ⚙️ ⛓ 👈 📋 👂 🔛 🌐 📢 💪 👈 🎰/💽. ///
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 10K bytes - Viewed (0) -
docs/zh/docs/advanced/behind-a-proxy.md
这是因为应用使用了以 `/api/v1` 为路径前缀的代理,前端要从 `/api/v1/openapi.json` 中提取 OpenAPI 概图。 ```mermaid graph LR browser("Browser") proxy["Proxy on http://0.0.0.0:9999/api/v1/app"] server["Server on http://127.0.0.1:8000/app"] browser --> proxy proxy --> server ``` /// tip | 提示 IP `0.0.0.0` 常用于指程序监听本机或服务器上的所有有效 IP。 /// API 文档还需要 OpenAPI 概图声明 API `server` 位于 `/api/v1`(使用代理时的 URL)。例如:
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 10.3K bytes - Viewed (0) -
compat/maven-compat/src/main/java/org/apache/maven/repository/legacy/LegacyRepositorySystem.java
} Proxy p = new Proxy(); p.setHost(proxy.getHost()); p.setProtocol(proxy.getProtocol()); p.setPort(proxy.getPort()); p.setNonProxyHosts(proxy.getNonProxyHosts()); p.setUserName(proxy.getUsername()); p.setPassword(proxy.getPassword());
Registered: Sun Sep 07 03:35:12 UTC 2025 - Last Modified: Fri Jun 06 14:28:57 UTC 2025 - 31.2K bytes - Viewed (0) -
docs/en/docs/deployment/https.md
* Otherwise, you might have to stop the TLS Termination Proxy momentarily, start the renewal program to acquire the certificates, then configure them with the TLS Termination Proxy, and then restart the TLS Termination Proxy. This is not ideal, as your app(s) will not be available during the time that the TLS Termination Proxy is off.
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/es/docs/deployment/https.md
* Esta es una de las razones por las que es muy útil cuando el mismo TLS Termination Proxy también se encarga del proceso de renovación del certificado.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 13K bytes - Viewed (0)