February 2024 Release

Highlights

• Client Byte Range Request Rule
• CORS Headers Rule Enhancements
• New Open Caching Dashboard for Service Providers
• Resolved Issues

Client Byte Range Request Rule

For Media/Site Delivery, a new Byte Range Request rule has been added to enable/disable support for byte range requests per hostname or path.

By default, range request support is enabled. When the range request support is disabled, the CDN ignores the range request and delivers the entire content.

This functionality helps support older devices that cannot easily stitch together content ranges.

Learn more here about this feature.

CORS Headers Rule Enhancements

In a site, if one resource loads resources from a different host, Cross-Origin Resource Sharing (CORS) headers can be used to inform the browser that it is safe to allow these cross-origin requests. When the CORS headers rule is configured, headers are dynamically added to the origin response, with explicit information about which cross-origin requests are allowed.

The CORS headers rule can now be set with both wildcard and authentication parameters, as illustrated below.

New Open Caching Dashboard for Service Providers

The new Open Caching Dashboard for Service Providers is now available, offering a detailed view of your network's performance, including traffic flow, efficiency, transaction response codes, and other essential metrics.

The dashboard provides a valuable tool for monitoring a CDN's operational status, identifying trends, and making informed decisions on the CDN’s performance.

Learn more about the new Open Caching Dashboard here.

Resolved Issue

• In the Service Provider Delivery Service Dashboard, the peak in the main summary panel now shows the total peak from all displayed Delivery Services, rather than only the highest Delivery Services peak.

For additional information about any of the above features or resolved issues, contact support@qwilt.com.