[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-27。"],[],[],null,["# Client connectivity and IP addresses\n\nMedia CDN supports modern networking protocols from the client to the\nedge, increasing throughput and reducing overall network latency.\n\nIP addressing\n-------------\n\nEach Edge Cache service that you configure has dedicated, anycast IPv4 and IPv6\naddresses, which are associated with each Edge Cache service that you create\nand are not shared with other customers.\n\n- After configuring an Edge Cache service, the IP addresses are assigned and become available.\n- Assigned addresses don't change for the life of a given Edge Cache service.\n- Creating a new Edge Cache service issues new IP addresses scoped to that service. IP addresses are not shared across your services.\n\nAll Media CDN services support IPv6 between clients and each\nedge node.\n| **Caution:** Deleting a service releases its IP addresses. These IP addresses might not be re-assigned to other services that you create.\n\n### Retrieve IP addresses\n\nTo retrieve the IP addresses assigned to an Edge Cache service: \n\n### gcloud\n\nUse the `gcloud edge-cache services` command. \n\n```\ngcloud edge-cache services describe MY_SERVICE\n``` \n\n```\n...\nipv4Addresses: [\"35.1.1.1\"]\nipv6Addresses: [\"2600:1901:0:fa74::\"]\n...\n```\n\nNotes:\n\n- Media CDN issues one IPv4 and one IPv6 address per service.\n- We recommend creating DNS records for both IP addresses (as A and AAAA records).\n- Configure your services to accept traffic for any domain names (hostnames) that you are using. When traffic is received for hosts without a `.routing.hostRules[].hosts` entry, Media CDN rejects the traffic with an HTTP 404 error.\n\nDepending on the geographies that your users are in, you might see more traffic\nto one protocol than another, based on user devices and ISP support in those\ngeographies.\n\nClient timeouts\n---------------\n\nThe following timeouts apply to client connections:\n\nFor origin timeouts and configuration, review the\n[failover and timeouts](/media-cdn/docs/origins#failover-and-timeouts) section\nof the origin documentation.\n\nClient request limits\n---------------------\n\nFor details about client request and response limits, see the\n[quotas and limits](/media-cdn/quotas) documentation.\n\nNetwork protocol support\n------------------------\n\nMedia CDN supports HTTP/3, HTTP/2, and HTTP/1.1 connections from\nclients. Media CDN supports both ALPN (Application Layer Protocol Negotiation)\nas well as the `Alt-Svc` (alternative service) HTTP response header for advertising\nprotocol support.\n\nNotes:\n\n- HTTP/2 (h2) is supported by default.\n- To enable HTTP/3 (QUIC), please contact your account team directly.\n- HTTPS, HTTP/2, and HTTP/3 require that a valid SSL (TLS) certificate is attached to your service.\n- Clients that do not support HTTP/2 or later automatically connect over HTTP/1.1\n\nFor origin protocol support, see [supported origins and protocols](/media-cdn/docs/origins).\n\nSupported SSL (TLS) versions\n----------------------------\n\nFor supported SSL (TLS) versions, see the\n[SSL documentation](/media-cdn/docs/ssl-certificates).\n\nTroubleshoot client connectivity\n--------------------------------\n\n- HTTP/2 (h2) protocol is supported only for clients connecting over TLS. This protocol doesn't support plaintext connections.\n- Clients only negotiate connections they support. New protocols are designed as *opt in* to provide backward compatibility.\n- If you have clients that have IPv6 addresses but are connecting to your Media CDN services over IPv4, it might be because the network between a Media CDN edge location and your user only supports IPv4.\n- Only HTTP/1.1 and later are supported as client protocols. HTTP/0.9 and HTTP/1.0 requests are rejected with an HTTP 426 (Upgrade Required) error."]]
