Media CDN no longer requires a HEAD request before fetching objects from your origin. This enhancement streamlines content delivery, reduces overhead, and improves overall performance. See origin requirements.

Media CDN supports multipart range requests, which enable users to request multiple non-contiguous segments of a file in a single HTTP request. This feature is Generally Available.

For more information, see Multipart range requests.

Media CDN supports flexible shielding. You can specify a single geographic region for origin shielding. This way, cache fills route through this configured region, offering a more efficient configuration for centralized origins than the default user-location-based approach. This feature is Generally Available.

For more information, see flexible shielding.

Media CDN supports multipart range requests, which enable users to request multiple non-contiguous segments of a file in a single HTTP request. This feature is in Preview.

For more information, see Multipart range requests.

You can use Autonomous System Numbers (ASN) based rules from Cloud Armor for Media CDN. ASN-based rules allow you to create security policies that specifically permit or deny traffic based on the ASN of the client requesting your content. This feature is Generally Available.

For more information, see Google Cloud Armor support.

Feature

You can use Network Threat Intelligence (NTI) from Cloud Armor in Edge Security Policies for Media CDN edge cache services for Enterprise users. NTI helps identify and block requests originating from known malicious IP addresses and networks. This feature is Generally Available.

For an example, see Example: Block traffic from known malicious IPs.

For more information, see Google Cloud Armor support.

You can use Autonomous System Numbers (ASN) based rules from Cloud Armor for Media CDN. ASN-based rules allow you to create security policies that specifically permit or deny traffic based on the ASN of the client requesting your content. This feature is in Preview.

For more information, see Google Cloud Armor support.

Media CDN supports a dedicated range of IPs for requests to external origin servers. IP allowlisting at the origin helps you restrict access to your content by only allowing traffic from Media CDN's IP addresses. This capability is Generally Available.

Media CDN supports flexible shielding. You can specify a single geographic region for origin shielding. This way, cache fills route through this configured region, which offers a more efficient configuration for centralized origins than the default user-location-based approach. This feature is in Preview.

For more information, see Flexible shielding.

You can use Network Threat Intelligence (NTI) from Cloud Armor in Edge Security Policies for Media CDN edge cache services for Enterprise users. NTI helps identify and block requests originating from known malicious IP addresses and networks. This feature is in Preview.

For an example, see Example: Block traffic from known malicious IPs.

Media CDN supports dynamic compression in General Availability.

In Preview, Media CDN supports dynamic compression for compressible content by using Brotli and gzip algorithms. Enabling dynamic compression can help you achieve faster page load times, speed up playback speed for video content, and optimize egress costs. For more information, see Enable dynamic compression.

HTTP method filtering for specific route rules is now Generally Available. You can now also implement such filtering by using the GUI.

Globally scoped Cloud Armor edge security policies for Layer 7 filtering are now Generally Available. For an example, see Example: Deny requests for cached content with specific headers.

By default, Media CDN proxies only GET, HEAD, and OPTIONS methods to your origin and filters out the methods that can modify your origin. In Preview, you can override this default behavior for a specific route rule by specifying other supported methods that you would like proxied to your origin.

You can use the globally scoped edge security policies of Cloud Armor for Layer 7 filtering. This feature is in Preview. For an example, see Example: Deny requests for cached content with specific headers.

Feature

Dual-token authentication is Generally Available. You can now enable this feature by using the Google Cloud Console in addition to the gcloud SDK and REST API. When this feature is enabled, Media CDN uses a short-duration token and a long-duration token to authenticate requests.

Media CDN supports content targeting, which helps you cache and deliver assets that are customized for your end-user contexts. It enables device characterization and geo-targeting, which are useful for implementing responsive websites, language customization, and currency settings.

The Media CDN capability to use a private S3-compatible bucket as an origin is now Generally Available. You can also use the GUI to configure such origins.

The following Media CDN features are now Generally Available:

• Configuring Media CDN to follow origin redirects
• Manipulating headers on a per-origin basis

For more information, see Failover and timeouts and Example: Failover with redirect following.

Media CDN now lets you add custom code to the request-response processing path by using Service Extensions plugins in Preview. Such customization unlocks a wide variety of lightweight use cases, such as header normalization and custom tokenization.

For more information, see Deploy Service Extensions plugins in Media CDN routes.

Media CDN now supports origin redirect following and origin header overrides in Preview.

You can improve performance and caching for frequent redirection by configuring origin redirect following in Media CDN. When configured, Media CDN follows origin redirect responses and caches the final retrieved object. For more information, see Configure following origin redirects.

You can also configure Media CDN to manipulate headers on a per-origin basis, which supports distinct host rewrites and static authorization headers for failover origins. For more information, see Failover and timeouts and Example: Failover with redirect following.

Media CDN now supports token-based client authentication and private external origin authentication for enhanced content protection and improved interoperability with multi-CDN and multi-cloud architectures in Preview.

Token-based authentication enables signing arbitrary data (like custom user identifiers), HMAC-based cryptography, and dual token exchange for token propagation through the duration of a playback session. For more information, see Prevent unauthorized distribution.

Private external origin authentication allows Media CDN to support private S3-compatible origins by dynamically generating signed requests with AWS Signature Version 4.

Media CDN now supports native logging and metrics for Common Media Client Data (CMCD) information that is transmitted through HTTP request headers or query parameters. CMCD provides visibility into the quality of service and experience for your end viewers.

For more information, see the CMCD row in Cache-specific logging fields and Media CDN metrics.

Cloud Media Edge is now Media CDN.

Cloud Media Edge is available in General Availability.

Cloud Media Edge now supports host, path, and tag based cache invalidation.

Cache tags allow you to invalidate the cache based on status codes, MIME type (Content-Type), and the origin the content was originally fetched from.

To learn how to use the gcloud SDK and REST API to invalidate cached responses, see the cache invalidation documentation.

Cloud Media Edge services now support the ability to match and rewrite incoming requests using pattern matching.

Pattern matching (or "wildcard matching") allows you to configure match rules with wildcard operators anywhere within a URL with pathTemplateMatch, capture path components, and rewrite URLs with pathTemplateRewrite before the request is sent to your origin.

Visit the pattern matching documentation to learn the pattern matching syntax, and see the suffix-matching example for how to match on file extensions.

Cloud Media Edge now supports connecting to private (non-public) Cloud Storage buckets. This allows you to restrict direct access to a storage bucket and/or only serve objects via your Media Edge services.

To learn how to configure private Cloud Storage access, visit the documentation.

Initial release of Cloud Media Edge. This product is in Private Preview.