每個 Secure Web Proxy 執行個體都需要一個 Cloud NAT 閘道，且該閘道只會為該區域的 Secure Web Proxy 端點啟用。在虛擬私有雲 (VPC) 網路區域中佈建的第一個安全 Web Proxy 也會佈建 Cloud NAT 閘道。Cloud NAT 閘道會為該虛擬網路和區域中的所有 Secure Web Proxy 執行個體啟用輸出功能。
僅支援 IPv4
Secure Web Proxy 僅支援 IPv4。不支援 IPv6。
內部 IP 位址屬於區域資源
Secure Web Proxy 會在區域內分配虛擬 IP 位址。虛擬 IP 位址只能在指派的區域中存取。此外，Secure Web Proxy 執行個體會在虛擬私有雲網路中的區域中佈建。因此，必須從 Secure Web Proxy 執行個體所在區域的子網路中分配 IPv4 位址。
以下說明 Secure Web Proxy 如何分配 IP 位址：
如果在佈建期間指定未保留的 IP 位址，系統就會使用該 IP 位址。
如果未指定 IP 位址，但指定了子網路和網路，系統會在指定的子網路中自動分配 IP 位址。
如果未指定 IP 位址、子網路和網路，系統會在預設網路的預設子網路中自動分配 IP 位址。
如果未符合上述任何條件，IP 配置作業就會失敗。
Secure Web Proxy 分配的 IP 位址是虛擬 IP，會指派給一組 Proxy，並散佈到區域內的多個單元格。安全網路 Proxy 會擔任明確的 Proxy 伺服器，因此用戶端必須連上虛擬 IP 位址，才能傳送出站 HTTP(S) 流量。可連線至虛擬 IP 位址的用戶端可透過下列方法存取安全 Web Proxy：
虛擬私有雲網路對等互連
共用虛擬私有雲
使用 Cloud VPN 或 Cloud Interconnect 連線至內部部署網路
支援的 HTTP 版本
支援 HTTP 0.9、1.0、1.1 和 2.0 版。不支援 HTTP 3。
共用虛擬私有雲中的 Secure Web Proxy
您只能在主機專案中部署 Secure Web Proxy。您無法在服務專案中部署 Secure Web Proxy。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Known limitations\n\nThis guide describes the known limitations of Secure Web Proxy.\n\nCloud NAT limitations\n---------------------\n\nEach Secure Web Proxy instance requires a Cloud NAT gateway that is enabled\nonly for the Secure Web Proxy endpoints in that region. The first\nSecure Web Proxy provisioned in a Virtual Private Cloud (VPC) network region\nalso provisions a Cloud NAT gateway. The Cloud NAT gateway\nenables egress for all Secure Web Proxy instances in that virtual network and\nregion.\n\nOnly IPv4 is supported\n----------------------\n\nSecure Web Proxy only supports IPv4. IPv6 is not supported.\n\nInternal IP addresses are regional\n----------------------------------\n\nSecure Web Proxy allocates virtual IP addresses within a region. The virtual\nIP addresses are reachable only in the region that they are assigned. Also,\nSecure Web Proxy instances are provisioned in a region within a\nVPC network. As a result, IPv4 addresses must be allocated from\nwithin a subnet of the region that the Secure Web Proxy instance is located\nin.\n\nThe following describes how Secure Web Proxy allocates IP addresses:\n\n- If an unreserved IP address is specified during provisioning, then that IP address is used.\n- If an IP address isn't specified but a subnet and network are specified, then an IP address is automatically allocated within the specified subnet.\n- If an IP address, subnet, and network aren't specified, then an IP address is automatically allocated within the default subnet of the default network.\n\nIP provisioning fails if none of the preceding items are met.\n\nThe IP addresses allocated by Secure Web Proxy are virtual IPs and are\nassigned to a group of proxies distributed across multiple cells within a\nregion. Secure Web Proxy acts as an explicit proxy server, which requires\nclients to have connectivity to the virtual IP address to pass egress HTTP(S)\ntraffic. Clients that have connectivity to the virtual IP address can access\nSecure Web Proxy through the following methods:\n\n- VPC Network Peering\n- Shared VPC\n- On-premises by using Cloud VPN or Cloud Interconnect\n\nSupported HTTP versions\n-----------------------\n\nHTTP versions 0.9, 1.0, 1.1, and 2.0 are supported. HTTP 3 is not supported.\n\nSecure Web Proxy in Shared VPC\n------------------------------\n\nYou can only deploy Secure Web Proxy in a host project. You cannot deploy\nSecure Web Proxy in a service project.\n\nSecurity rule creation race condition\n-------------------------------------\n\nWhen you create a large number of Secure Web Proxy security rules in\nparallel by using Terraform, you may encounter a race condition. As a\nworkaround, use the `terraform apply` command with `--parallelism=1`.\n\nSecure Web Proxy in Private Service Connect\n-------------------------------------------\n\nSecure Web Proxy does not support `RoutingMode` set to\n`NEXT_HOP_ROUTING_MODE` with Private Service Connect service\nattachment.\n\nSupported number of frontend ports\n----------------------------------\n\nSecure Web Proxy supports a maximum of five frontend ports. You can't change\nthe selected ports after [creating a gateway](/secure-web-proxy/docs/quickstart#create-a-gateway)."]]
