Expansion Variables

Overview

Inserting Expansion Variables into the settings of certain configuration policies is an advanced method for fine tuning the delivery of your content over the Highwinds CDN Network.

Expansion Variables are an advanced feature you can take advantage of whether you're interacting programmatically with the APIs or via StrikeTracker.

A complete list of the expansion variables currently available for use on the Highwinds CDN is listed below.

Expansion Variables

Use Case: Redirect HTTP Traffic to HTTPS

In the example below we're going to update a Scope to include a configuration policy paired with a few expansion variables in order to redirect all HTTP traffic on that Scope to HTTPS.

Specifically, we will update the Scope with Scope ID matching "654321" to include the Cache Rule (dynamicCacheRule), which is a Delivery policy, and pair that policy with a handful of the expansion variables from the list of expansion variables to redirect HTTP traffic to HTTPS.

1. Set the value for the headers parameter to include the %client.request.host%, client.request.fullfilepath%, and %client.request.params% expansion variables.
2. Set the pathFilter parameter to http://*.
3. Set the statusCode parameter to 301.

API Request:

Method: PUT

Authorization: Bearer token

URL: https://striketracker.highwinds.com/api/v1/accounts/{account_id}/hosts/{host_id}/configuration/{scope_id}

Request Body:

{
  "dynamicCacheRule": [
    {
      "comment": "Redirect all HTTP traffic to HTTPS",
      "headerFilter": "*", 
      "headers": "Location: https://%client.request.host%%client.request.fullfilepath%%client.request.params%", 
      "methodFilter": "*", 
      "pathFilter": "http://*", 
      "statusCode": "301"
    }
  ]
}