Using Wowza Media Server with our HTTP Streaming Solutions

Applies To:

HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.

Wowza Media Server's default caching behavior interferes with the functionality of our HTTP streaming solutions. The easiest way to ensure that a valid cache configuration is used for our HTTP streaming solutions is to create a custom cache policy on the HTTP Large platform for playlist, media, and segment files.

Rules Engine must be purchased separately. For more information, please contact your CDN account manager.

The custom caching policy that should be defined in Rules Engine is described below.

Create the following custom caching policy under a single "select first match" section.

CEConditional Expression	Match Condition	Features
if	Match: URL Path Extension Literal Result: match Value: manifest f4m f4x abst bootstrap Ignore Case: yes	Force Internal Max-age Status: 200 Value/Units: 2 seconds External Max-Age Status: 200 Value/Units: -1 Seconds Ignore Origin No-Cache Codes: 200 Expires Header Treatment Treatment: Remove
else if	Match Condition: URL Path Extension Literal Result: match Value: ts f4f Ignore Case: yes	Force Internal Max-age Status: 200 Value/Units: 360 Seconds External Max-Age Status: 200 Value/Units: -1 Seconds Ignore Origin No-Cache Codes: 200 Expires Header Treatment Treatment: Remove
else if	Match Condition: URL Path Wildcard Result: match Value: /QualityLevels/Fragments* Ignore Case: yes Relative To: root	Force Internal Max-age Status: 200 Value/Units: 360 Seconds External Max-Age Status: 200 Value/Units: -1 Seconds Ignore Origin No-Cache Codes: 200 Expires Header Treatment Treatment: Remove
else if	Match Condition: URL Path Filename Wildcard Result: match Value: Seg-Frag* Ignore Case: yes	Force Internal Max-age Status: 200 Value/Units: 360 Seconds External Max-Age Status: 200 Value/Units: -1 Seconds Ignore Origin No-Cache Codes: 200 Expires Header Treatment Treatment: Remove
else if	Match Condition: URL Path Extension Literal Result: match Value: m3u8 Ignore Case: yes	Bypass Cache Enabled: yes

Once the above draft has been created, it should be converted to a policy and then deployed to the desired environment. After which, it will undergo a review process. Track a the progress of a deploy request by clicking the "View deploy request" link corresponding to the desired environment from the Rules Engine page.

Wowza Media Server Configuration

Setting up a Wowza Media Server requires Wowza Push Publishing AddOn 3.5 or higher. The readme provided with this addon provides detailed instructions on how to leverage the RTMP profile for use with our CDN service.