如此一來，應用就能知道自己的對外 URL、是否使用 HTTPS、網域為何等資訊。

這在正確處理重新導向等情境時很有用。

/// tip

你可以在文件 [在代理後方 - 啟用代理轉發標頭](../advanced/behind-a-proxy.md#enable-proxy-forwarded-headers) 中了解更多。

///

## 重點回顧 { #recap }

擁有 **HTTPS** 非常重要，而且在多數情況都相當**關鍵**。作為開發者，你在 HTTPS 上的大部分投入其實是**理解這些概念**及其運作方式。

一旦掌握了**給開發者的 HTTPS 基礎**，你就能輕鬆組合並設定不同工具，讓一切管理變得簡單。

由於使用了相對 URL，若你的 API 位於 `https://example.com/`，那它會指向 `https://example.com/token`；但若你的 API 位於 `https://example.com/api/v1/`，那它會指向 `https://example.com/api/v1/token`。

使用相對 URL 很重要，能確保你的應用在像是[在 Proxy 後方](../../advanced/behind-a-proxy.md)這類進階情境中仍能正常運作。

///

這個參數不會建立該端點／「路徑操作」，而是宣告 `/token` 將是客戶端用來取得 token 的 URL。這些資訊會出現在 OpenAPI，並被互動式 API 文件系統使用。

我們很快也會建立實際的路徑操作。

/// info

* Remove outdated net.experimental.kubernetes.io/proxy-mode and net.beta.kubernetes.io/proxy-mode annotations from kube-proxy. ([#40585](https://github.com/kubernetes/kubernetes/pull/40585), [@cblecker](https://github.com/cblecker))

FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Dhttp.maxConnections=20"

# Force the JVM to use IPv4 stack
if [ "x$FESS_USE_IPV4" != "x" ]; then
  FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Djava.net.preferIPv4Stack=true"
fi

# proxy
if [ "x$FESS_PROXY_HOST" != "x" ]; then
  FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Dhttp.proxyHost=$FESS_PROXY_HOST"
  FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Dhttps.proxyHost=$FESS_PROXY_HOST"
fi
if [ "x$FESS_PROXY_PORT" != "x" ]; then

    ExecutionException e = assertThrows(ExecutionException.class, chain::get);
    assertThat(e.getCause()).isInstanceOf(BadFutureRuntimeException.class);
  }

  /** Proxy to throw a {@link RuntimeException} out of the {@link #get()} method. */
  public static class BadFuture extends SimpleForwardingListenableFuture<Integer> {
    protected BadFuture(ListenableFuture<Integer> delegate) {

    ExecutionException e = assertThrows(ExecutionException.class, chain::get);
    assertThat(e.getCause()).isInstanceOf(BadFutureRuntimeException.class);
  }

  /** Proxy to throw a {@link RuntimeException} out of the {@link #get()} method. */
  public static class BadFuture extends SimpleForwardingListenableFuture<Integer> {
    protected BadFuture(ListenableFuture<Integer> delegate) {

// connect happens.
func newClient(endpoint string) NetLocker {
	u, err := url.Parse(endpoint)
	if err != nil {
		panic(err)
	}

	tr := &http.Transport{
		Proxy:                 http.ProxyFromEnvironment,
		MaxIdleConnsPerHost:   1024,
		WriteBufferSize:       32 << 10, // 32KiB moving up from 4KiB default
		ReadBufferSize:        32 << 10, // 32KiB moving up from 4KiB default

│   └── main.py
├── Dockerfile
└── requirements.txt
```

#### 在 TLS 终止代理后面 { #behind-a-tls-termination-proxy }

如果你在 Nginx 或 Traefik 等 TLS 终止代理（负载均衡器）后面运行容器，请添加 `--proxy-headers` 选项，这会通过 FastAPI CLI 告诉 Uvicorn 信任该代理发送的标头，表明应用运行在 HTTPS 后等。

```Dockerfile
CMD ["fastapi", "run", "app/main.py", "--proxy-headers", "--port", "80"]
```

#### Docker 缓存 { #docker-cache }

### CSI Proxy for Windows

The CSI Proxy for Windows is being promoted to beta along with the 1.19 release. This CSI Proxy enables CSI Drivers to run on Windows by allowing containers in Windows to perform privileged storage operations. At beta, the CSI Proxy for Windows supports storage drivers using direct attached disks and SMB.

### Dashboard v2

http.proxy.port=8080
# Username for HTTP proxy authentication.
http.proxy.username=
# Password for HTTP proxy authentication.
http.proxy.password=
# Maximum size (bytes) for HTTP file uploads.
http.fileupload.max.size=262144000
# Threshold size (bytes) for HTTP file upload buffering.
http.fileupload.threshold.size=262144
# Maximum number of files allowed per HTTP upload.
http.fileupload.max.file.count=10