Delivery Service URL(s)

{{::url}}

General Configuration Settings
XML_ID (Key) *
This id becomes a part of the CDN service domain in the form `http://cdn.service-key.company.com/`. Must be all lowercase, no spaces or special characters. May contain dashes.
Required Too Long Must be a valid DNS label (no special characters, capital letters, periods, underscores, or spaces and cannot begin or end with a hyphen)

### Current Value

    {{::dsCurrent.xmlId}}

Display Name *
Name of the service that appears in the Traffic portal. No character restrictions.
Required Too Long

### Current Value

    {{::dsCurrent.displayName}}

Active *
Whether or not this Delivery Service is active on the CDN and is capable of traffic.
Required

### Current Value

    {{::dsCurrent.active ? 'Active' : 'Not Active'}}

Content Routing Type *
DNS is the standard routing type for most CDN services. HTTP Redirect is a specialty routing service that is primarily used for video and large file downloads where localization and latency are significant concerns. A "Live" routing type should be used for all live services.
See Delivery Service Types.
Required View Details

### Current Value

    {{::dsCurrent.type}}

Tenant *
Name of company or division of company who owns account. Allows you to group your services and control access. Tenants are setup as a simple hierarchy where you may create parent / child accounts.
Required View Details

### Current Value

    {{::dsCurrent.tenant}}

CDN *
The CDN to which the Delivery Service belongs.
Required View Details

### Current Value

    {{::dsCurrent.cdnName}}

Origin Server Base URL *
The Origin Server’s base URL which includes the protocol (http or https). Example: `http://movies.origin.com`. Must be a domain only, no directories or IP addresses
Required Must start with http:// or https:// and be followed by a valid hostname with an optional port (no trailing slash) View Details

### Current Value

    {{::dsCurrent.orgServerFqdn}}

Protocol *
The protocol with which to serve this Delivery Service to the clients:

HTTP
  Deliver only HTTP traffic
HTTPS
  Deliver only HTTPS traffic
HTTP AND HTTPS
  Deliver both types of traffic
HTTP TO HTTPS
  Redirect HTTP traffic to use HTTPS

Required

### Current Value

    {{magicNumberLabel(protocols, dsCurrent.protocol)}}

Topology
A topology is used to determine the caching layers and path to a delivery service's origin.
View Details

### Current Value

    {{::dsCurrent.topology}}

Service Category
The type of content being delivered. Some examples are linear and vod.
View Details

### Current Value

    {{::dsCurrent.serviceCategory}}

Long Description 1
Free text field not currently used in configuration.

### Current Value

    {{::dsCurrent.longDesc}}

Long Description 2
Free text field not currently used in configuration.

### Current Value

    {{::dsCurrent.longDesc1}}

Long Description 3
Free text field not currently used in configuration.

### Current Value

    {{::dsCurrent.longDesc2}}

DSCP
The DSCP * value with which to mark IP packets outbound to the client.
Required

### Current Value

    {{magicNumberLabel(dscps, dsCurrent.dscp)}}

Profile
Only used if a Delivery Service uses configurations that specifically require a profile. Example: Multi-Site Origin configurations would require a Delivery Service Profile to be used.
View Details

### Current Value

    {{::dsCurrent.profileName}}

Info URL
Free text field used to enter a URL which provides information about the service.
Invalid URL Too Long

### Current Value

    {{::dsCurrent.infoUrl}}

Check Path
A path (e.g. `/crossdomain.xml`) with which to verify the connection to the origin server. This can be used by Check Extension scripts to do periodic health checks against the Delivery Service.
Too Long

### Current Value

    {{::dsCurrent.checkPath}}

Origin Shield
Add another forward proxy upstream of the mid caches. Example: `go_direct=true` will allow the Mid to hit the origin directly instead of failing if the origin shield is down.

###### Warning

This feature is experimental, use with caution!

Too Long

### Current Value

    {{::dsCurrent.originShield}}

Cache Configuration Settings
Max Origin Connections
The maximum number of connections allowed to the origin. Enter `0` to indicate no maximum.
Too Small (must be greater than or equal to 0)

### Current Value

    {{::dsCurrent.maxOriginConnections}}

Max Request Header Bytes
The maximum size (in bytes) of the request headers for this particular delivery service. The default value is `0` which will limit the request headers size (in bytes) to the value defined by the proxy.config.http.request_header_max_size parameter.
Too Small (must be greater than or equal to 0) Too Big (must be lesser than or equal to 2147483647)

### Current Value

    {{::dsCurrent.maxRequestHeaderBytes}}

Signing Algorithm
Type of URL signing method to sign the URLs:

None
  URLs will not be signed within this Delivery Service
URL Signature Keys
  URL Signature token-based authentication is enabled for this Delivery Service.
URI Signing Keys
  URI Signing token-based authentication is enabled for this Delivery Service.

See Token Based Authentication

### Current Value

    {{magicNumberLabel(signingAlgos, dsCurrent.signingAlgorithm)}}

Range Request Handling *
How to treat range requests.

- Do not cache (ranges requested from files that are already cached due to a non range request can still be served)
- Use the `background_fetch` plugin.
- Use the `cache_range_requests` plugin.
- Use the `slice` plugin.

Required

### Current Value

    {{magicNumberLabel(rrhs, dsCurrent.rangeRequestHandling)}}

Range Slice Block Size
The block size in bytes that is used for the slice plugin for range requests. Must be between `262144` - `33554432`. Can only be set if the Range Request Handling is set to `Use the slice plugin`
Too Small (must be greater than or equal to 262144) Too Large (must be smaller than or equal to 33554432) Required

### Current Value

    {{::dsCurrent.rangeSliceBlockSize}}

Query String Handling *
How to treat query parameter strings in request URLs:

- Use in cache key and hand up to origin: Each URL is considered unique if and only if the entire URL (i.e. including any query parameter string string) is unique.
- Do not use in cache key, but pass up to origin: Two URLs that are the same except for the query parameter string will match and cache HIT, while the origin still sees original query parameter string in the request.
- Drop at edge: Two URLs that are the same except for the query string will match and cache HIT, while the origin will not see original query string in the request.

###### Note:

Choosing to drop query parameter strings at the edge will preclude the use of a Regex Remap Expression. See Regex Remap Expression
To set the qstring without the use of regex remap, or for further options, See Qstring Handling

Required

### Current Value

    {{magicNumberLabel(qStrings, dsCurrent.qstringIgnore)}}

Edge Header Rewrite Rules
For non topology-based delivery services, headers can be added or altered at the edge layer of the CDN. You must tell us three things: the action, the header name, and the header value. The action will tell us whether we are adding, removing, or replacing headers. The header name and header value will determine the full header text. Edge header rewrite values will be added before we respond to a request from a client. Examples include:

- Action: Set
- Header Name: X-CDN
- Header Value: Foo

See Edge Header Rewrite Rules.
Only applicable with non topology-based delivery services

### Current Value

    {{::dsCurrent.edgeHeaderRewrite}}

Mid Header Rewrite Rules
For non topology-based delivery services, headers can be added or altered at the mid layer of the CDN. You must tell us three things: the action, the header name, and the header value. The action will tell us whether we are adding, removing, or replacing headers. The header name and header value will determine the full header text. Mid header rewrite values will be added before we make a request further up the chain in the server hierarchy (ie. to the origin). Examples include:

- Action: Set
- Header Name: Host
- Header Value: code_abc123

See Mid Header Rewrite Rules.
Only applicable with non topology-based delivery services

### Current Value

    {{::dsCurrent.midHeaderRewrite}}

First Header Rewrite Rules
For topology-based delivery services, headers can be added or altered at the first layer (aka edge layer) of the CDN. You must tell us three things: the action, the header name, and the header value. The action will tell us whether we are adding, removing, or replacing headers. The header name and header value will determine the full header text. First header rewrite values will be added before we respond to a request from a client. Examples include:

- Action: Set
- Header Name: Host
- Header Value: code_abc123

See First Header Rewrite Rules.
Only applicable with topology-based delivery services

### Current Value

    {{::dsCurrent.firstHeaderRewrite}}

Inner Header Rewrite Rules
For topology-based delivery services, headers can be added or altered at the inner layer of the CDN. You must tell us three things: the action, the header name, and the header value. The action will tell us whether we are adding, removing, or replacing headers. The header name and header value will determine the full header text. Inner header rewrite values will be added before we make a request further up the chain in the server hierarchy. Examples include:

- Action: Set
- Header Name: Host
- Header Value: code_abc123

See Inner Header Rewrite Rules.
Only applicable with topology-based delivery services

### Current Value

    {{::dsCurrent.innerHeaderRewrite}}

Last Header Rewrite Rules
For topology-based delivery services, headers can be added or altered at the last layer of the CDN. You must tell us three things: the action, the header name, and the header value. The action will tell us whether we are adding, removing, or replacing headers. The header name and header value will determine the full header text. Last header rewrite values will be added before we make a request further up the chain in the server hierarchy (ie. to the origin). Examples include:

- Action: Set
- Header Name: Host
- Header Value: code_abc123

See Last Header Rewrite Rules.
Only applicable with topology-based delivery services

### Current Value

    {{::dsCurrent.lastHeaderRewrite}}

Regex remap expression
Allows remapping of incoming requests URL using regex pattern matching to search/replace text.
Too Long

###### Note

You will not be able to save a Regex Remap Expression if you have Query String Handling set to drop query strings at the edge. See Regex Remap Expression

### Current Value

    {{::dsCurrent.regexRemap}}

Raw remap text
For HTTP and DNS Delivery Services, this will get added to the end of the remap line verbatim on cache servers. For ANY_MAP Delivery Services this is the entire remap line.
No Line Breaks

### Current Value

    {{::dsCurrent.remapText}}

Use Multi-Site Origin Feature *
Enables/disables the Multi-Site Origin feature for this Delivery Service.
See Multi-Site Origin.
Required

### Current Value

    {{::dsCurrent.multiSiteOrigin ? 'Use Multi-Site Origin' : 'Do not use Multi-Site Origin'}}

Cache URL Expression
Allows you to manipulate the cache key of the incoming requests. Normally, the cache key is the origin domain. This can be changed so that multiple services can share a cache key, can also be used to preserve cached content if service origin is changed.

###### Note

This only works with Edge-tier cache servers running ATS version 6 and earlier. This must be empty if using ATS 7 and / or the cachekey plugin.

See ATS documentation on cacheurl

###### Warning

This field is deprecated, and is subject to removal in upcoming releases. It is recommended that this be left blank.

Too Long

### Current Value

    {{::dsCurrent.cacheurl}}

Routing Configuration Settings
Routing Name *
The routing name to use for the delivery FQDN, e.g. `routing-name.deliveryservice.cdn-domain`. It must be a valid hostname without periods.
Required Too Long Must be a valid DNS label (no special characters, capital letters, periods, underscores, or spaces and cannot begin or end with a hyphen)

### Current Value

    {{::dsCurrent.routingName}}

Deep Caching *
Enables clients to be routed to the closest possible deep edge caches on a per Delivery Service basis.
See Deep Caching
Required

### Current Value

    {{::dsCurrent.deepCachingType}}

IPv6 Routing Enabled *
Enabeld by default, disabling this allows you to turn off CDN responses to IPv6 requests
Required

### Current Value

    {{::dsCurrent.ipv6RoutingEnabled ? 'Enabled' : 'Disabled'}}

EDNS0 Client Subnet Enabled *
Disabled by default, enabling this enables EDNS0 client subnet on the Delivery Service level.
Required

### Current Value

    {{::dsCurrent.ecsEnabled ? 'Enabled' : 'Disabled'}}

Initial Dispersion *
Determines number of machines content will be placed on within a cache group. Setting too high will result in poor caching performance. An initial dispersion of 1 is equivalent to "no dispersion".
Required

### Current Value

    {{::dsCurrent.initialDispersion}}

Regional Geoblocking *
Define regional geo-blocking rules for Delivery Services in a JSON format and set this to 'Enabled' to use "Regional Geoblocking". See Regional Geo-blocking
Required

### Current Value

    {{::dsCurrent.regionalGeoBlocking ? 'Enabled' : 'Disabled'}}

Anonymous Blocking *
Enable this to block anonymized IP addresses (e.g. TOR exit nodes) for this Delivery Service.

###### Note:

Requires Geolocation provider's Anonymous IP database.

Required

### Current Value

    {{::dsCurrent.anonymousBlockingEnabled ? 'Enabled' : 'Disabled'}}

Geolocation Provider *
Choose which Geolocation database provider - company that collects data on the location of IP addresses - to use.
Required

### Current Value

    {{magicNumberLabel(geoProviders, dsCurrent.geoProvider)}}

Geo Miss Default Latitude *
Default latitude for this Delivery Service. When client localization fails for both Coverage Zone and Geo Lookup, the client will be routed as if it was at this latitude.
Required Too Small (must be greater than or equal to -90) Too Big (must be less than or equal to 90)

### Current Value

    {{::dsCurrent.missLat}}

Geo Miss Default Longitude *
Default longitude for this Delivery Service. When client localization fails for both Coverage Zone and Geo Lookup, the client will be routed as if it was at this longitude.
Required Too Small (must be greater than or equal to -180) Too Big (must be less than or equal to 180)

### Current Value

    {{::dsCurrent.missLong}}

Geo Limit *
Some services are intended to be limited by geography. The possible settings are:

None
  Do not limit by geography.
Coverage Zone File only
  If the requesting IP is not in the Coverage Zone File, do not serve the request.
Coverage Zone File and Country Code(s)
  If the requesting IP is not in the Coverage Zone File or not in the United States, do not serve the request.

Required

### Current Value

    {{magicNumberLabel(geoLimits, dsCurrent.geoLimit)}}

Geo Limit Countries
How (if at all) is this service to be limited by geography. Example Country Codes: CA, IN, PR.
Too Long

### Current Value

    {{::dsCurrent.geoLimitCountries}}

Geo Limit Redirect URL
Traffic Router will redirect to this URL when Geo Limit check fails.
See GeoLimit Failure Redirect feature...
Invalid URL

### Current Value

    {{::dsCurrent.geoLimitRedirectURL}}

HTTP Bypass FQDN
Traffic Router will redirect to this FQDN (with the same path) when the Max Mbps or Max Tps for this Delivery Service are exceeded.
Must be a valid FQDN

### Current Value

    {{::dsCurrent.httpBypassFqdn}}

DNS Bypass TTL
TTL for the DNS bypass domain or IP address when thresholds are exceeded.

### Current Value

    {{::dsCurrent.dnsBypassTtl}}

Max DNS Answers
See ATS documentation on Max DNS Answers: HTTP-routed Delivery Service
Too Small (must be greater than or equal to 0)

### Current Value

    {{::dsCurrent.maxDnsAnswers}}

Delivery Service DNS TTL
The TTL on the DNS record for the Traffic Router A and AAAA records. Setting too high or too low will result in poor caching performance.

### Current Value

    {{::dsCurrent.ccrDnsTtl}}

Global Max Mbps
The maximum bits per second this Delivery Service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS Delivery Service, the Bypass Ipv4 or Ipv6 will be used (depending on whether this was an A or AAAA request), and for HTTP Delivery Services the Bypass FQDN will be used.
Too Small (must be greater than or equal to 0)

### Current Value

    {{::dsCurrent.globalMaxMbps}}

Global Max Tps
The maximum transactions this Delivery Service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS Delivery Service, the Bypass Ipv4 or Ipv6 will be used (depending on whether this was an A or AAAA request), and for HTTP Delivery Services the Bypass FQDN will be used.
Too Small (must be greater than or equal to 0)

### Current Value

    {{::dsCurrent.globalMaxTps}}

Fair Queueing Pacing Rate Bps
The maximum bytes per second a cache will deliver on any single TCP connection. This uses the Linux kernel's Fair Queuing (`setsockopt(SO_MAX_PACING_RATE)`) to limit the rate of delivery.
Too Small (must be greater than or equal to 0)

### Current Value

    {{::dsCurrent.fqPacingRate}}

Traffic Router Additional Response Headers
List of header name:value pairs. One name:value pair per line. Listed pairs will be included in all Traffic Router HTTP(S) responses.

### Current Value

    {{::dsCurrent.trResponseHeaders}}

Traffic Router Log Request Headers
List of header keys. One header key per line. Listed headers will be included in Traffic Router access log entries under the `rh=` token.

### Current Value

    {{::dsCurrent.trRequestHeaders}}

Consistent Hash Regex
Regex used to extract parts of the request path using grouping in order to build a consistent request string to be used for cache selection. If this field is set on a steering delivery service, it will override the regex set on the target delivery services.
See Pattern-Based Consistent Hashing
Too Long Test Regex

### Current Value

    {{::dsCurrent.consistentHashRegex}}

Consistent Hash Query Param #{{$index + 1}}
When Traffic Router performs a "consistent hash" on a client request to find an Edge-tier cache server to which to redirect them, it can optionally take into account any number of query parameters. This field defines them, formally as a Set but often represented as an Array/List due to encoding limitations. That is, if the Consistent Hashing Query Parameters on a Delivery Service are test and a client makes a request for `/?test=something` they will be directed to a different cache server than a different client that requests `/?test=somethingElse`, but the same cache server as a client that requests `/?test=something&quest=somethingToo`.
No spaces

### Current Value

    Consistent Hash Query Param #{{$index + 1}}: {{::dsCurrent.consistentHashQueryParams[$index]}}