Media CDN supports modern networking protocols from the client to the edge, increasing throughput and reducing overall network latency.
Each Edge Cache service that you configure has dedicated, anycast IPv4 and IPv6 addresses, which are associated with each Edge Cache service that you create and are not shared with other customers.
- After configuring an Edge Cache service, the IP addresses are assigned and become available.
- Assigned addresses don't change for the life of a given Edge Cache service.
- Creating a new Edge Cache service issues new IP addresses scoped to that service. IP addresses are not shared across your services.
All Media CDN services support IPv6 between clients and each edge node.
Retrieve IP addresses
To retrieve the IP addresses assigned to an Edge Cache service:
gcloud edge-cache services command.
gcloud edge-cache services describe MY_SERVICE
... ipv4Addresses: ["22.214.171.124"] ipv6Addresses: ["2600:1901:0:fa74::"] ...
- Media CDN issues one IPv4 and one IPv6 address per service.
- We recommend creating DNS records for both IP addresses (as A and AAAA records).
- Configure your services to accept traffic for any domain names
(hostnames) that you are using. When traffic is received for hosts without
.routing.hostRules.hostsentry, Media CDN rejects the traffic with an HTTP 404 error.
Depending on the geographies that your users are in, you might see more traffic to one protocol than another, based on user devices and ISP support in those geographies.
The following timeouts apply to client connections:
|Timeout||Maximum duration||Response code||Description|
|Maximum request duration||5 minutes||HTTP 408 (Request Timeout)||The maximum duration of a single request-response.|
|Header timeout||10 seconds||HTTP 408 (Request Timeout)||How long the client has to send the full set of request headers.|
For origin timeouts and configuration, review the failover and timeouts section of the origin documentation.
Client request limits
For details about client request and response limits, see the quotas and limits documentation.
Network protocol support
Media CDN supports HTTP/3, HTTP/2, and HTTP/1.1 connections from
clients. Media CDN supports both ALPN (Application Layer Protocol Negotiation)
as well as the
Alt-Svc (alternative service) HTTP response header for advertising
|Protocol||Supported||SSL (TLS) Required|
|HTTP/3 (IETF QUIC)||Yes||Yes|
|HTTPS (HTTP/1.1 over TLS)||Yes||Yes|
- HTTP/2 (h2) is supported by default.
- To enable HTTP/3 (QUIC), please contact your account team directly.
- HTTPS, HTTP/2, and HTTP/3 require that a valid SSL (TLS) certificate is attached to your service.
- Clients that do not support HTTP/2 or later automatically connect over HTTP/1.1
For origin protocol support, see supported origins and protocols.
Supported SSL (TLS) versions
For supported SSL (TLS) versions, see the SSL documentation.
Troubleshoot client connectivity
- HTTP/2 (h2) protocol is supported only for clients connecting over TLS. This protocol doesn't support plaintext connections.
- Clients only negotiate connections they support. New protocols are designed as opt in to provide backward compatibility.
- 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.
- 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.