You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficcontrol.apache.org by mi...@apache.org on 2018/05/23 01:39:45 UTC
[incubator-trafficcontrol] 04/04: minor changes
This is an automated email from the ASF dual-hosted git repository.
mitchell852 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-trafficcontrol.git
commit a0e3bb760f744f176193d111736a1ef234691fe9
Author: Ashish Timilsina <as...@comcast.com>
AuthorDate: Tue May 22 14:22:55 2018 -0600
minor changes
---
docs/source/admin/traffic_ops/using.rst | 305 +++++++++++----------
.../app/src/traffic_portal_properties.json | 88 +++---
2 files changed, 201 insertions(+), 192 deletions(-)
diff --git a/docs/source/admin/traffic_ops/using.rst b/docs/source/admin/traffic_ops/using.rst
index 62e40f1..c7273e5 100644
--- a/docs/source/admin/traffic_ops/using.rst
+++ b/docs/source/admin/traffic_ops/using.rst
@@ -292,154 +292,163 @@ Delivery Service
The fields in the Delivery Service view are:
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Name | Description [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Active | Whether or not this delivery service is active on the CDN and is capable of traffic. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| 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 :ref:`rl-ds-types`. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Key (XML ID) | 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. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Display Name | Name of the service that appears in the Traffic portal. No character restrictions. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| 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. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| CDN | The CDN in which the delivery service belongs [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Routing Name | The routing name to use for the delivery FQDN, i.e. ``<routing-name>.<deliveryservice>.<cdn-domain>``. It must be a valid hostname without periods. Typical values would be ccr, edge and cdn. [2]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Protocol | Services that use "HTTP and HTTPS" will be able to deliver both types of traffic. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DSCP Tag | The Differentiated Services Code Point (DSCP) value to mark IP packets to the client with. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Signing Algorithm | Type of URL signing method to sign the URLs. See :ref:`rl-signed-urls`. [...]
-| | [...]
-| | - null: token based auth is not enabled for this delivery service. [...]
-| | - “url_sig”: URL Sign token based auth is enabled for this delivery service. [...]
-| | - “uri_signing”: URI Signing token based auth is enabled for this delivery service. [...]
-| | [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Deep Caching | Enables clients to be routed to the closest possible "deep" edge caches on a per Delivery Service basis. [...]
-| | See `Deep Caching <http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#deep-caching-deep-coverage-zone-topology>`_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Query String Handling | How to treat query strings: [...]
-| | [...]
-| | - 0 use in cache key and hand up to origin: Each unique query string is treated as a unique URL. [...]
-| | - 1 Do not use in cache key, but pass up to origin: 2 URLs that are the same except for the query string will match and cache HIT, while the origin still sees original query string in the request. [...]
-| | - 2 Drop at edge: 2 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 strings at the edge will preclude the use of a Regex Remap Expression. See :ref:`rl-regex-remap`. [...]
-| | [...]
-| | To set the qstring without the use of regex remap, or for further options, see :ref:`rl-qstring-handling`. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geolocation Provider | Choose which Geolocation database provider, company that collects data on the location of IP addresses, to use [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Limit | Some services are intended to be limited by geography. The possible settings are are: [...]
-| | [...]
-| | - None: Do not limit by geography. [...]
-| | - CZF only: If the requesting IP is not in the Coverage Zone File, do not serve the request. [...]
-| | - CZF + US: If the requesting IP is not in the Coverage Zone File or not in the United States, do not serve the request. [...]
-| | [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Limit Countries | How (if at all) is this service to be limited by geography. Example: CA, IN, PR [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Limit Redirect URL | (For HTTP routed delivery services only) This is the URL, Traffic Router will redirect to when Geo Limit check fails. See :ref:`rl-tr-ngb` [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Regional Geoblocking | (For HTTP routed delivery services only) Define regional geo-blocking rules for delivery services in a JSON format and set it to True/False. [...]
-| | See `regional geo-blocking <http://traffic-control-cdn.readthedocs.io/en/latest/admin/quick_howto/regionalgeo.html#configure-regional-geo-blocking-rgb>`_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| IPv6 Routing Enabled | Default is "True", entering "False" allows you to turn off CDN response to IPv6 requests [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Range Request Handling | How to treat range requests: [...]
-| | [...]
-| | - 0: Do not cache (ranges requested from files that are already cached due to a non range request will be a HIT) [...]
-| | - 1: Use the `background_fetch <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/background_fetch.en.html>`_ plugin. [...]
-| | - 2: Use the cache_range_requests plugin. [...]
-| | [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DNS Bypass IP | (For DNS routed delivery services only) IPv4 address to overflow requests when the the max Bps or Max Tps for this delivery service are exceeded. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DNS Bypass IPv6 | (For DNS routed delivery services only) IPv6 address to overflow requests when the the max Bps or Max Tps for this delivery service are exceeded. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DNS Bypass Cname | (For DNS routed delivery services only) Domain name to overflow requests when the the max Bps or Max Tps for this delivery service are exceeded. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DNS Bypass TTL | TTL for the DNS bypass domain or IP when threshold exceeded. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Fair Queuing Pacing Rate Bps | The maximum bytes per second a cache will delivery on any single TCP connection. This uses the Linux kernel’s Fair Queuing setsockopt (SO_MAX_PACING_RATE) to limit the rate of delivery. Traffic exceeding this speed will only be rate-limited and not diverted. This option requires net.core.default_qdisc = fq in /etc/sysctl.conf. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| 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 a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Global Max TPS | The maximum transactions per se 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 a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Max DNS Answers | This is available only for DNS Content Routing Types. It is used to restrict the number of cache IP addresses that the CCR will hand back. A numeric value from 1 to 15 which determines how many caches your content will be spread across in a particular site. When a customer requests your content they will get 1 to 15 IP addresses back they can use. These are rotated in each response. Ideally the number will reflect the amount of traffic. 1 = [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Delivery Service DNS TTL | (For DNS routed delivery services only) The Time To Live on the DNS record for the Traffic Router A and AAAA records. Default value is 30 seconds. Setting too high or too low will result in poor caching performance. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Initial Dispersion | This is available only for HTTP Content Routing Types. Determines number of machines content will be placed on within a cache group. Default is 1, Setting too high will result in poor caching performance. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Origin Server Base URL | The Origin Server’s base URL. This includes the protocol (http or https). Example: ``http://movies.origin.com`` [...]
-| | Must be a domain only, no directories or IP addresses [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Use Multi Site Origin Feature | Enable the Multi Site Origin feature for this delivery service. Is the Multi Site Origin feature enabled for this delivery service (True/False). See :ref:`rl-multi-site-origin` [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Delivery Service Profile | Only used if a delivery service uses configurations that specifically require a profile. Example: MSO configurations or cachekey plugin would require a ds profile to be used. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Miss Default Latitude | Default Latitude for this delivery service. When client localization fails for both Coverage Zone and Geo Lookup, this the client will be routed as if it was at this lat. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Miss Default Longitude | Default Longitude for this delivery service. When client localization fails for bot Coverage Zone and Geo Lookup, this the client will be routed as if it was at this long. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Edge Header Rewrite Rules | Headers can be added or altered at each layer of the CDN. You must tell us four things: the action, the header name, the header value, and the direction to apply. 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. The direction will determine whether we add it before we respond to a request or before we make a request further up the chain in the [...]
-| | [...]
-| | - Action: Set [...]
-| | - Header Name: X-CDN [...]
-| | - Header Value: Foo [...]
-| | - Direction: Edge Response to Client [...]
-| | [...]
-| | See :ref:`rl-header-rewrite`. [1]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Mid Header Rewrite Rules | Headers can be added or altered at each layer of the CDN. You must tell us four things: the action, the header name, the header value, and the direction to apply. 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. The direction will determine whether we add it before we respond to a request or before we make a request further up the chain in the [...]
-| | [...]
-| | - Action: Set [...]
-| | - Header Name: Host [...]
-| | - Header Value: code_abc123 [...]
-| | - Direction: Mid Request to Origin [...]
-| | [...]
-| | See :ref:`rl-header-rewrite`. [1]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Traffic Router Additional Response Headers | List of header name:value pairs separated by __RETURN__. Listed pairs will be included in all TR HTTP responses. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Traffic Router Log Request Headers | List of header keys separated by __RETURN__. Listed headers will be included in TR access log entries under the “rh=” token. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Regex remap expression | Allows remapping of incoming requests URL using regex pattern matching to search/replace text. [...]
-| | See `ATS documentation on regex_remap <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_remap.en.html>`_. [1]_ [...]
-| | [...]
-| | **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 :ref:`rl-regex-remap`. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| 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:** Only valid in ATS 6.X and earlier. Must be empty if using ATS 7.X and/or the `cachekey plugin <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cachekey.en.html>`_. [1]_ [...]
-| | [...]
-| | See `ATS documentation on cacheurl <https://docs.trafficserver.apache.org/en/6.2.x/admin-guide/plugins/cacheurl.en.html>`_. [1]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Raw remap text | For HTTP and DNS delivery services, this will get added to the end of the remap line on the cache verbatim. For ANY_MAP delivery services this is the remap line. [1]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Long Description | A short text field that describes the purpose of the delivery service and will be displayed in the portal as a description field. For example, you can use this field to describe your service. To be consumed from the APIs by downstream tools. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Long Description 1 | Free text field not currently used in configuration. For example, you can use this field to describe your customer type. To be consumed from the APIs by downstream tools. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Long Description 2 | Free text field not currently used in configuration. To be consumed from the APIs by downstream tools. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Info URL | Free text field allowing you to enter a URL which provides information about the service. To be consumed from the APIs by downstream tools. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Check Path | A path (ex: /crossdomain.xml) to verify the connection to the origin server with. This can be used by Check Extension scripts to do periodic health checks against the delivery service. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Origin Shield (Pipe Delimited String) | 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. Experimental Feature. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Logs Enabled | Allows you to turn on/off logging for the service [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Name | Description [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Active | Whether or not this delivery service is active on the CDN and is capable of traffic. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| 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 :ref:`rl-ds-types`. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Key (XML ID) | 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. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Display Name | Name of the service that appears in the Traffic portal. No character restrictions. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| 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. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| CDN | The CDN in which the delivery service belongs to. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Routing Name | The routing name to use for the delivery FQDN, i.e. ``<routing-name>.<deliveryservice>.<cdn-domain>``. It must be a valid hostname without periods. [2]_ [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Protocol | The protocol to serve this delivery service to the clients with: [...]
+| | [...]
+| | - HTTP: Delivery only HTTP traffic [...]
+| | - HTTPS: Delivery only HTTPS traffic [...]
+| | - HTTP AND HTTPS: Deliver both types of traffic. [...]
+| | - HTTP TO HTTPS: Delivery HTTP traffic as HTTPS traffic [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| DSCP Tag | The Differentiated Services Code Point (DSCP) value to mark IP packets to the client with. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Signing Algorithm | Type of URL signing method to sign the URLs: [...]
+| | [...]
+| | - null: token based auth is not enabled for this delivery service. [...]
+| | - “url_sig”: URL Sign token based auth is enabled for this delivery service. [...]
+| | - “uri_signing”: URI Signing token based auth is enabled for this delivery service. [...]
+| | [...]
+| | See :ref:`rl-signed-urls`. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Deep Caching | Enables clients to be routed to the closest possible "deep" edge caches on a per Delivery Service basis. [...]
+| | See `Deep Caching <http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#deep-caching-deep-coverage-zone-topology>`_ [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Query String Handling | How to treat query strings: [...]
+| | [...]
+| | - 0 use in cache key and hand up to origin: Each unique query string is treated as a unique URL. [...]
+| | - 1 Do not use in cache key, but pass up to origin: 2 URLs that are the same except for the query string will match and cache HIT, while the origin still sees original query string in the request. [...]
+| | - 2 Drop at edge: 2 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 strings at the edge will preclude the use of a Regex Remap Expression. See :ref:`rl-regex-remap`. [...]
+| | [...]
+| | To set the qstring without the use of regex remap, or for further options, see :ref:`rl-qstring-handling`. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Geolocation Provider | Choose which Geolocation database provider, company that collects data on the location of IP addresses, to use. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Anonymous Blocking | Set to true to enable blocking of anonymous IPs for this delivery service. **Note:** Requires Geolocation provider's Anonymous IP database. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Geo Limit | Some services are intended to be limited by geography. The possible settings are: [...]
+| | [...]
+| | - None: Do not limit by geography. [...]
+| | - CZF only: If the requesting IP is not in the Coverage Zone File, do not serve the request. [...]
+| | - CZF + US: If the requesting IP is not in the Coverage Zone File or not in the United States, do not serve the request. [...]
+| | [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Geo Limit Countries | How (if at all) is this service to be limited by geography. Example Country Codes: CA, IN, PR. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Geo Limit Redirect URL | Traffic Router will redirect to this URL when Geo Limit check fails. See :ref:`rl-tr-ngb` [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Regional Geoblocking | Define regional geo-blocking rules for delivery services in a JSON format and set it to True/False. [...]
+| | See `regional geo-blocking <http://traffic-control-cdn.readthedocs.io/en/latest/admin/quick_howto/regionalgeo.html#configure-regional-geo-blocking-rgb>`_ [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| IPv6 Routing Enabled | Default is "True", entering "False" allows you to turn off CDN response to IPv6 requests [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Range Request Handling | How to treat range requests: [...]
+| | [...]
+| | - 0: Do not cache (ranges requested from files that are already cached due to a non range request will be a HIT) [...]
+| | - 1: Use the `background_fetch <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/background_fetch.en.html>`_ plugin. [...]
+| | - 2: Use the cache_range_requests plugin. [...]
+| | [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| DNS Bypass IP | IPv4 address to overflow requests when the Max Bps or Max Tps for this delivery service exceeds. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| DNS Bypass IPv6 | IPv6 address to overflow requests when the Max Bps or Max Tps for this delivery service exceeds. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| DNS Bypass CNAME | Domain name to overflow requests when the Max Bps or Max Tps for this delivery service exceeds. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| DNS Bypass TTL | TTL for the DNS bypass domain or IP when threshold exceeds [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| HTTP Bypass FQDN | Traffic Router will redirect to this FQDN (with the same path) when the Max Bps or Max Tps for this delivery service exceeds. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Delivery Service DNS TTL | The Time To Live on the DNS record for the Traffic Router A and AAAA records. Setting too high or too low will result in poor caching performance. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Fair Queuing Pacing Rate Bps | The maximum bytes per second a cache will delivery on any single TCP connection. This uses the Linux kernel’s Fair Queuing setsockopt (SO_MAX_PACING_RATE) to limit the rate of delivery. Traffic exceeding this speed will only be rate-limited and not diverted. This option requires net.core.default_qdisc = fq in /etc/sysctl.conf. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| 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 a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Global Max TPS | The maximum transactions per se 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 a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Max DNS Answers | It is used to restrict the number of cache IP addresses that the CCR will hand back. A numeric value from 1 to 15 which determines how many caches your content will be spread across in a particular site. When a customer requests your content they will get 1 to 15 IP addresses back they can use. These are rotated in each response. Ideally the number will reflect the amount of traffic. 1 = trial account with very little traffic, 2 = small prod [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Initial Dispersion | Determines number of machines content will be placed on within a cache group. Setting too high will result in poor caching performance. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| 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 [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Use Multi Site Origin Feature | Set True/False to enable/disable the Multi Site Origin feature for this delivery service. See :ref:`rl-multi-site-origin` [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Delivery Service Profile | Only used if a delivery service uses configurations that specifically require a profile. Example: MSO configurations or cachekey plugin would require a ds profile to be used. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Geo Miss Default Latitude | Default Latitude for this delivery service. When client localization fails for both Coverage Zone and Geo Lookup, this the client will be routed as if it was at this lat. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Geo Miss Default Longitude | Default Longitude for this delivery service. When client localization fails for bot Coverage Zone and Geo Lookup, this the client will be routed as if it was at this long. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Edge Header Rewrite Rules | Headers can be added or altered at each layer of the CDN. You must tell us four things: the action, the header name, the header value, and the direction to apply. 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. The direction will determine whether we add it before we respond to a request or before we make a request further up the chain in the [...]
+| | [...]
+| | - Action: Set [...]
+| | - Header Name: X-CDN [...]
+| | - Header Value: Foo [...]
+| | - Direction: Edge Response to Client [...]
+| | [...]
+| | See :ref:`rl-header-rewrite`. [1]_ [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Mid Header Rewrite Rules | Headers can be added or altered at each layer of the CDN. You must tell us four things: the action, the header name, the header value, and the direction to apply. 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. The direction will determine whether we add it before we respond to a request or before we make a request further up the chain in the [...]
+| | [...]
+| | - Action: Set [...]
+| | - Header Name: Host [...]
+| | - Header Value: code_abc123 [...]
+| | - Direction: Mid Request to Origin [...]
+| | [...]
+| | See :ref:`rl-header-rewrite`. [1]_ [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Traffic Router Additional Response Headers | List of header name:value pairs separated by __RETURN__. Listed pairs will be included in all TR HTTP responses. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Traffic Router Log Request Headers | List of header keys separated by __RETURN__. Listed headers will be included in TR access log entries under the “rh=” token. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Regex remap expression | Allows remapping of incoming requests URL using regex pattern matching to search/replace text. [...]
+| | See `ATS documentation on regex_remap <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_remap.en.html>`_. [1]_ [...]
+| | [...]
+| | **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 :ref:`rl-regex-remap`. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| 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:** Only valid in ATS 6.X and earlier. Must be empty if using ATS 7.X and/or the `cachekey plugin <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cachekey.en.html>`_. [1]_ [...]
+| | [...]
+| | See `ATS documentation on cacheurl <https://docs.trafficserver.apache.org/en/6.2.x/admin-guide/plugins/cacheurl.en.html>`_. [1]_ [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Raw remap text | For HTTP and DNS delivery services, this will get added to the end of the remap line on the cache verbatim. For ANY_MAP delivery services this is the remap line. [1]_ [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Long Description | Free text field that describes the purpose of the delivery service and will be displayed in the portal as a description field. For example, you can use this field to describe your service. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Long Description 2 | Free text field not currently used in configuration. For example, you can use this field to describe your customer type. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Long Description 3 | Free text field not currently used in configuration. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Info URL | Free text field allowing you to enter a URL which provides information about the service. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Check Path | A path (ex: /crossdomain.xml) to verify the connection to the origin server with. This can be used by Check Extension scripts to do periodic health checks against the delivery service. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Origin Shield (Pipe Delimited String) | 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. Experimental Feature. [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
+| Logs Enabled | Allows you to turn on/off logging for the service [...]
++--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
.. [1] These fields are not validated by Traffic Ops to be correct syntactically, and can cause Traffic Server to not start if invalid. Please use with caution.
.. [2] It is not recommended to change the Routing Name of a Delivery Service after deployment because this changes its Delivery FQDN (i.e. ``<routing-name>.<deliveryservice>.<cdn-domain>``), which means that SSL certificates may need to be updated and clients using the Delivery Service will need to be transitioned to the new Delivery URL.
diff --git a/traffic_portal/app/src/traffic_portal_properties.json b/traffic_portal/app/src/traffic_portal_properties.json
index fe30dc7..2b869ba 100644
--- a/traffic_portal/app/src/traffic_portal_properties.json
+++ b/traffic_portal/app/src/traffic_portal_properties.json
@@ -135,7 +135,7 @@
"DNS": {
"routingName": "cdn",
"dscp": 0,
- "ipv6RoutingEnabled": false,
+ "ipv6RoutingEnabled": true,
"rangeRequestHandling": 0,
"qstringIgnore": 0,
"multiSiteOrigin": false,
@@ -153,7 +153,7 @@
"routingName": "cdn",
"deepCachingType": "NEVER",
"dscp": 0,
- "ipv6RoutingEnabled": false,
+ "ipv6RoutingEnabled": true,
"rangeRequestHandling": 0,
"qstringIgnore": 0,
"multiSiteOrigin": false,
@@ -171,7 +171,7 @@
"STEERING": {
"dscp": 0,
"routingName": "cdn",
- "ipv6RoutingEnabled": false,
+ "ipv6RoutingEnabled": true,
"logsEnabled": false,
"geoProvider": 0,
"geoLimit": 0,
@@ -183,19 +183,19 @@
"_comments": "This is the text used to configure delivery service field titles/descriptions",
"active": {
"title": "Active",
- "desc": "When this is set to false Traffic Router will not serve DNS or HTTP responses for this delivery service."
+ "desc": "Whether or not this delivery service is active on the CDN and is capable of traffic."
},
"anonymousBlockingEnabled": {
"title": "Anonymous Blocking",
- "desc": "Set to true to enable blocking of anonymous IPs for this delivery service -- requires MaxMind's Anonymous IP database."
+ "desc": "Set to true to enable blocking of anonymous IPs for this delivery service. <b>Note:<b> Requires Geolocation provider's Anonymous IP database."
},
"cacheurl": {
"title": "Cache URL expression",
- "desc": "Cache URL rule to apply to this delivery service.<br><br>See <a href=\"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cacheurl.en.html\" target=\"_blank\">ATS documentation on cacheurl...</a>"
+ "desc": "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.<br><b>Note:</b> Only valid in ATS 6. X and earlier. Must be empty if using ATS 7. X and / or the <a href = \"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cachekey.en.html\" target=\"_blank\">cac [...]
},
"ccrDnsTtl": {
"title": "Delivery Service DNS TTL",
- "desc": "The Time To Live on the DNS record for the Traffic Router A and AAAA records."
+ "desc": "The Time To Live on the DNS record for the Traffic Router A and AAAA records. Setting too high or too low will result in poor caching performance."
},
"cdnId": {
"title": "CDN",
@@ -207,51 +207,51 @@
},
"deepCachingType": {
"title": "Deep Caching",
- "desc": "When to do deep caching for this delivery service.<br><br>See <a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#rl-deep-cache\" target=\"_blank\">Deep Caching</a> for more details..."
+ "desc": "Enables clients to be routed to the closest possible deep edge caches on a per Delivery Service basis.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#rl-deep-cache\" target=\"_blank\">See Deep Caching</a>"
},
"displayName": {
"title": "Display Name",
- "desc": "A human-readable name for the delivery service."
+ "desc": "Name of the service that appears in the Traffic portal. No character restrictions."
},
"dnsBypassCname": {
"title": "DNS Bypass CNAME",
- "desc": "Description required"
+ "desc": "Domain name to overflow requests when the Max Bps or Max Tps for this delivery service exceeds."
},
"dnsBypassIp": {
"title": "DNS Bypass IP",
- "desc": "This is the address to respond to A requests with when the max Bps or Max Tps for this delivery service are exceeded."
+ "desc": "IPv4 address to overflow requests when the Max Bps or Max Tps for this delivery service exceeds."
},
"dnsBypassIp6": {
"title": "DNS Bypass IPv6",
- "desc": "This is the address to respond to AAAA requests with when the max Bps or Max Tps for this delivery service are exceeded."
+ "desc": "IPv6 address to overflow requests when the Max Bps or Max Tps for this delivery service exceeds."
},
"dnsBypassTtl": {
"title": "DNS Bypass TTL",
- "desc": "Description required"
+ "desc": "TTL for the DNS bypass domain or IP when threshold exceeds."
},
"dscp": {
"title": "DSCP",
- "desc": "The DSCP value to mark IP packets to the client with."
+ "desc": "The Differentiated Services Code Point (DSCP) value to mark IP packets to the client with."
},
"edgeHeaderRewrite": {
"title": "Edge Header Rewrite Rules",
- "desc": "Header Rewrite rules to apply for this delivery service at the EDGE tier.<br><br>See <a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-header-rewrite\" target=\"_blank\">Header Rewrite Options and DSCP...</a>"
+ "desc": "Headers can be added or altered at each layer of the CDN. You must tell us four things: the action, the header name, the header value, and the direction to apply. 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. The direction will determine whether we add it before we respond to a request or before we make a request further up the chain in the server hierarchy. Example [...]
},
"geoLimitRedirectURL": {
"title": "Geo Limit Redirect URL",
- "desc": "This is the URL Traffic Router will redirect to when Geo Limit Failure.<br><br>See <a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#rl-tr-ngb\" target=\"_blank\">GeoLimit Failure Redirect</a> feature..."
+ "desc": "Traffic Router will redirect to this URL when Geo Limit check fails.<br><br>See <a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#rl-tr-ngb\" target=\"_blank\">GeoLimit Failure Redirect</a> feature..."
},
"geoLimit": {
"title": "Geo Limit",
- "desc": "Some services are intended to be limited by geography.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\" target=\"_blank\">See more...</a>"
+ "desc": "Some services are intended to be limited by geography. The possible settings are:<br><br><ul><li>None: Do not limit by geography.</li><li>CZF only: If the requesting IP is not in the Coverage Zone File, do not serve the request.</li><li>CZF + US: If the requesting IP is not in the Coverage Zone File or not in the United States, do not serve the request.</li><br>"
},
"geoLimitCountries": {
"title": "Geo Limit Countries",
- "desc": "Description required"
+ "desc": "How (if at all) is this service to be limited by geography. Example Country Codes: CA, IN, PR."
},
"geoProvider": {
"title": "Geolocation Provider",
- "desc": "Description required"
+ "desc": "Choose which Geolocation database provider, company that collects data on the location of IP addresses, to use."
},
"globalMaxMbps": {
"title": "Global Max Mbps",
@@ -267,43 +267,43 @@
},
"httpBypassFqdn": {
"title": "HTTP Bypass FQDN",
- "desc": "This is the FQDN Traffic Router will redirect to (with the same path) when the max Bps or Max Tps for this delivery service are exceeded."
+ "desc": "Traffic Router will redirect to this FQDN (with the same path) when the Max Bps or Max Tps for this delivery service exceeds."
},
"infoUrl": {
"title": "Info URL",
- "desc": "Info URL for this delivery service."
+ "desc": "Free text field used to enter a URL which provides information about the service."
},
"initialDispersion": {
"title": "Initial Dispersion",
- "desc": "Description required"
+ "desc": "Determines number of machines content will be placed on within a cache group. Setting too high will result in poor caching performance."
},
"ipv6RoutingEnabled": {
"title": "IPv6 Routing Enabled",
- "desc": "When set to true, the Traffic Router will respond to AAAA DNS requests for the routed name of this delivery service. Otherwise, only A records will be served."
+ "desc": "Default is True, entering False allows you to turn off CDN response to IPv6 requests"
},
"logsEnabled": {
"title": "Logs Enabled",
- "desc": "Description required"
+ "desc": "Allows you to turn on/off logging for the service"
},
"longDesc": {
"title": "Long Description",
- "desc": "Long description for this delivery service."
+ "desc": "Free text field that describes the purpose of the delivery service and will be displayed in the portal as a description field."
},
"longDesc1": {
"title": "Long Description 2",
- "desc": "Long description 2 for this delivery service."
+ "desc": "Free text field not currently used in configuration. For example, you can use this field to describe your customer type."
},
"longDesc2": {
"title": "Long Description 3",
- "desc": "Long description 3 for this delivery service."
+ "desc": "Free text field not currently used in configuration."
},
"maxDnsAnswers": {
"title": "Max DNS Answers",
- "desc": "Description required"
+ "desc": "It is used to restrict the number of cache IP addresses that the CCR will hand back. A numeric value from 1 to 15 which determines how many caches your content will be spread across in a particular site. When a customer requests your content they will get 1 to 15 IP addresses back they can use. These are rotated in each response. Ideally the number will reflect the amount of traffic. 1 = trial account with very little traffic, 2 = small production service. Add 1 more [...]
},
"midHeaderRewrite": {
"title": "Mid Header Rewrite Rules",
- "desc": "Header Rewrite rules to apply for this delivery service at the EDGE tier.<br><br>See <a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-header-rewrite\" target=\"_blank\">Header Rewrite Options and DSCP...</a>"
+ "desc": "Headers can be added or altered at each layer of the CDN. You must tell us four things: the action, the header name, the header value, and the direction to apply. 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. The direction will determine whether we add it before we respond to a request or before we make a request further up the chain in the server hierarchy. Example [...]
},
"missLat": {
"title": "Geo Miss Default Latitude",
@@ -315,39 +315,39 @@
},
"multiSiteOrigin": {
"title": "Use Multi Site Origin Feature",
- "desc": "Enable the Multi Site Origin feature for this delivery service.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-multi-site-origin\" target=\"_blank\">See Multi Site Origin...</a>"
+ "desc": "Set True/False to enable/disable the Multi Site Origin feature for this delivery service.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-multi-site-origin\" target=\"_blank\">See Multi Site Origin.</a>"
},
"orgServerFqdn": {
"title": "Origin Server Base URL",
- "desc": "The Origin Server’s base URL. This includes the protocol (http or https). Example: http://movies.origin.com"
+ "desc": "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"
},
"originShield": {
"title": "Origin Shield (Pipe Delimited String)",
- "desc": "Description required"
+ "desc": "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. Experimental Feature."
},
"profileId": {
"title": "Delivery Service Profile",
- "desc": "Description required"
+ "desc": "Only used if a delivery service uses configurations that specifically require a profile. Example: MSO configurations or cachekey plugin would require a ds profile to be used."
},
"protocol": {
"title": "Protocol",
- "desc": "The protocol to serve this delivery service to the clients with.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\" target=\"_blank\">See more...</a>"
+ "desc": "The protocol to serve this delivery service to the clients with:<br><br> <ul><li>HTTP: Deliver only HTTP traffic</li><li>HTTPS: Deliver only HTTPS traffic </li><li>HTTP AND HTTPS: Deliver both types of traffic</li><li>HTTP TO HTTPS: Deliver HTTP traffic as HTTPS traffic. </li></ul><br>"
},
"qstringIgnore": {
"title": "Query String Handling",
- "desc": "How to treat query strings.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\" target=\"_blank\">See more...</a>"
+ "desc": "How to treat query strings:<br><br><ul><li>0 use in cache key and hand up to origin: Each unique query string is treated as a unique URL.</li><li>1 Do not use in cache key, but pass up to origin: 2 URLs that are the same except for the query string will match and cache HIT, while the origin still sees original query string in the request.</li><li>2 Drop at edge: 2 URLs that are the same except for the query string will match and cache HIT, while the origin will not s [...]
},
"rangeRequestHandling": {
"title": "Range Request Handling",
- "desc": "How to treat range requests.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\" target=\"_blank\">See more...</a>"
+ "desc": "How to treat range requests.<br><br><ul><li>0: Do not cache (ranges requested from files that are already cached due to a non range request will be a HIT)</li><li>1: Use the <a href=\"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/background_fetch.en.html\" target=\"_blank\">background_fetch plugin.</a></li><li>2: Use the cache_range_requests plugin.</li></ul>"
},
"regexRemap": {
"title": "Regex remap expression",
- "desc": "Regex Remap rule to apply to this delivery service at the Edge tier.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\" target=\"_blank\">See more...</a>"
+ "desc": "Allows remapping of incoming requests URL using regex pattern matching to search/replace text.<br><br><a href=\"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_remap.en.html\" target=\"_blank\">See ATS documentation on regex remap</a><br><b>Note:</b> 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. <a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin [...]
},
"regionalGeoBlocking": {
"title": "Regional Geoblocking",
- "desc": "Description required"
+ "desc": "Define regional geo-blocking rules for delivery services in a JSON format and set it to True/False. <a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/quick_howto/regionalgeo.html#configure-regional-geo-blocking-rgb\" target=\"_blank\">See Regional Geo-blocking</a>"
},
"remapText": {
"title": "Raw remap text",
@@ -359,27 +359,27 @@
},
"signingAlgorithm": {
"title": "Signing Algorithm",
- "desc": "Description required"
+ "desc": "Type of URL signing method to sign the URLs:<br><ul><li>null: token based auth is not enabled for this delivery service.</li><li>“url_sig”: URL Sign token based auth is enabled for this delivery service.</li><li>“uri_signing”: URI Signing token based auth is enabled for this delivery service.</li></ul><br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-signed-urls\" target=\"_blank\">See Token Based Authentication</a>"
},
"tenantId": {
"title": "Tenant",
- "desc": "By selecting a tenant for the delivery service, you restrict access of that delivery service to only those users that belong to the same tenant or a parent tenant."
+ "desc": "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."
},
"trRequestHeaders": {
"title": "Traffic Router Log Request Headers",
- "desc": "Description required"
+ "desc": "List of header keys separated by __RETURN__. Listed headers will be included in TR access log entries under the “rh=” token."
},
"trResponseHeaders": {
"title": "Traffic Router Additional Response Headers",
- "desc": "Description required"
+ "desc": "List of header name:value pairs separated by __RETURN__. Listed pairs will be included in all TR HTTP responses."
},
"typeId": {
"title": "Content Routing Type",
- "desc": "The type of content routing this delivery service will use.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-ds-types\" target=\"_blank\">See Delivery Service Types....</a>"
+ "desc": "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.<br><br><a href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-ds-types\" target=\"_blank\">See Delivery Service Types.</a>"
},
"xmlId": {
"title": "Key (XML ID)",
- "desc": "A unique string that identifies this delivery service."
+ "desc": "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."
}
}
}
--
To stop receiving notification emails like this one, please contact
mitchell852@apache.org.