-
An A record maps a hostname to an IPv4 address.
-
A AAAA record maps a hostname to an IPv6 address.
-
This type of URL identifies a resource (e.g., asset or file) using the following format: scheme://server/path/resource (e.g., http://cdn.mydomain.com/sales/presentation.pdf).
-
Allows a media player to dynamically switch between bit rate streams of varying quality levels, in order to provide an optimal viewing experience based on a client’s bandwidth and CPU usage.
-
This type of record maps a hostname to an IP address. A records are used for IPv4 addresses, while AAAA records are used for IPv6 addresses.
-
The Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.
-
ADN Only: Optimizes communication between our network and your web servers. Each customer origin configuration is assigned a failover list of ADN gateway servers that identify the servers that will provide optimal delivery to your customer origin.
-
A virtual record that maps a hostname to another hostname or FQDN.
-
This product provides a variety of reports that range from basic CDN usage statistics to real-time data to in-depth trend analysis on key metrics. This suite consists of the following modules: Core, Custom, Advanced Content Analytics, Real-Time Statistics, and Edge Performance Analytics.
-
TCP/IP: Refers to the layer that supports applications and processes. For example, it contains protocols (e.g., HTTP and FTP) that facilitate communication across a network.
-
A file is the most commonly known example of an asset. Refers to any collection of data that is typically stored as a single unit on a storage unit (e.g., disk drive). An example of an asset that is not physically stored on a disk drive occurs when dynamically generated content is not cached.
-
Identifies a name server that contains all records for a specific DNS zone and is trusted to be accurate. A recursive name server can forward DNS requests to this type of name server.
-
Token-Based Authentication requires the use of an encryption key to encrypt and decrypt token values. There are two types of encryption keys, which are a primary and a backup key. Both of these keys can be used to encrypt and decrypt token values.
-
Limits the rate at which content can be downloaded.
-
Refers to data that can either be true or false.
-
Refers to a request for partial content. This type of request is typically used to retrieve a large asset in smaller segments. This technique is employed by HTTP Progressive Download to avoid long buffering times.
-
Refers to the storage of data to improve data delivery performance. When used in reference to our CDN, it refers to the temporary storage of an asset on an edge server or an origin shield server. Cache increases the speed through which that particular edge server can deliver that asset for subsequent requests.
-
A relative path that uniquely identifies an asset for the purpose of caching. Our edge servers use this relative path when checking for cached content and when caching content. By default, a cache-key will not contain query string parameters.
-
Indicates that the requested content could not be served immediately from the edge of our network because it either hasn't been cached or its TTL has expired. This type of request is forwarded to an origin server.
-
Refers to the HTTP response headers (e.g., Cache-Control and Expires) that define the length of time that content will be cached. This type of policy may be set through HTTP response headers or through HTTP Rules Engine.
-
Refers to the process that occurs when a request for stale content requires that our edge servers check for a new version of the requested content on the origin server.
-
Our content delivery network (CDN) is responsible for the efficient and secure delivery of data from an origin to requesters. It consists of points-of-presence (POPs) that are placed at critical network and geographical locations around the world. This allows us to place content at the edge of the Internet allowing for faster downloads by your end-users.
-
Refers to a system-defined hostname that is specific to your customer account and a CDN service.
-
This service was discontinued on 11/12/2018. This storage solution is designed to store content on behalf of the Media Ingest feature.
-
This type of identifier in the CDN URL indicates that requested asset should be retrieved from the CDN origin server. A CDN origin identifier is indicated by "00" as the starting two numbers in the CDN URL path.
-
Refers to a server used for CDN storage. The close proximity of our CDN origin servers to our POPs ensures optimal conditions for the delivery of data from CDN storage to your users.
-
Refers to our storage solution. Store content on our servers to ensure data availability and fast data delivery.
-
A system-defined URL that points to a CDN hostname. A CDN URL allows content delivery via our network. Simplify your CDN setup by also creating an edge CNAME configuration which potentially allows you to deliver traffic via the CDN using the same links as your current setup.
-
Refers to the portion of the CDN URL that appears after the CDN hostname. It identifies a CDN or customer origin and provides the relative path to a specific folder or asset.
-
A Canonical Name (CNAME) record is used to indicate that a hostname is an alias of another hostname. A CNAME record must be registered on a Domain Name System (DNS). This term should not be confused with edge CNAME.
-
Rules Engine: Refers to the logic (i.e., IF and ELSE IF) through which one or more match conditions identify a type of request.
-
This URL segment of a CDN URL identifies where the request should be directed. This relative path starts directly after the CDN hostname. The proper syntax for a content access point is "/yyAN," where "yy" stands for the origin identifier and "AN" stands for a customer account number. A content access point for a customer origin also includes a directory that identifies it.
-
Our content delivery network (CDN) is responsible for the efficient and secure delivery of data from an origin to requesters. It consists of points-of-presence (POPs) that are placed at critical network and geographical locations around the world. This allows us to place content at the edge of the Internet allowing for faster downloads by your end-users.
-
Identifies/classifies the data contained in a file.
-
This feature restricts access according to the country from which content was requested.
-
Identifies a customer by a system-defined account number (e.g., 0001). This account number consists of alphanumeric characters. A customer's account number is displayed in the upper-right hand corner of the MCC.
-
Refers to a CDN configuration that identifies one or more web servers that will serve as the source from which content may be delivered via the CDN.
-
Refers to a CDN configuration that identifies one or more web servers that will serve as the source from which content may be delivered via the CDN.
-
This type of identifier in the CDN URL indicates that requested asset should be retrieved from the customer origin server. A customer origin identifier is indicated by "80" as the starting two numbers in the CDN URL path.
-
Refers to a web server external to our network that will serve as the source from which content will be delivered. This type of web server must be defined in a customer origin configuration.
-
The purpose of a Distributed Denial of Service (DDoS) attack is to prevent content delivery by making a network device (e.g., customer origin server) unavailable. A Denial of Service attack is considered "distributed" when it is performed by more than one person/machine.
-
The Defend product is designed to provide protection against application layer and volumetric attacks. This product offering consists of the Web Application Firewall (WAF) and the Rate Limiting features.
-
Identifies the environment through which your content will be efficiently delivered to your users.
-
Rules Engine: Refers to a request to push out a policy to either the Staging or Production environment. This request triggers an automated review process. If a policy fails automated validation, then it will undergo manual review.
-
A dimension describes an attribute of a request and is typically used to correlate the desired set of requests with metrics.
-
A hierarchical and distributed naming system for any resource connected to the Internet. This system includes the capability to translate hostnames into IP addresses.
-
The DNS Health Checks module checks the health of a server or domain by polling it with an HTTP or TCP request. These health checks are essential when load balancing or failing traffic over multiple servers.
-
Refers to the hierarchical tree structure through which domains are organized.
-
Defines the length of time, in seconds, that a DNS record will be cached by a recursive nameserver.
-
The purpose of a domain is to identify a resource (e.g., computer) on the Internet. A domain is organized into a hierarchy. This hierarchy is explored using "www.example.com" as an example. "www" is considered a third-level domain. "example" is considered a second-level domain. "com" is considered a top-level domain. The above hierarchy is critical when resolving a domain, since the top-level domain and subsequent domains will be resolved by different authoritative name servers.
-
A hierarchical and distributed naming system for any resource connected to the Internet. This system includes the capability to translate hostnames into IP addresses.
-
Refers to the hierarchical tree structure through which domains are organized.
-
Identifies the top and second-level domains associated with the CDN hostname. An example of a domain root is "google.com."
-
Rules Engine: Refers to a working copy of one or more rules that identify requests and the set of actions that can be applied to them. Once a draft is completed, it should be finalized and converted into a policy.
-
Establishes a playback window that allows a user to pause/resume, rewind, and fast forward a live stream.
-
This streaming solution facilitates HLS and/or MPEG-DASH playback of live or on-demand content. A live stream may be pushed to this service via RTMP.
-
Refers to content that is generated or modified as it is requested. This allows for an interactive experience and/or for content to be tailored to the user. For example, a web page may leverage PHP to generate a personalized web page that leverages information from a database.
-
Allows a media player to dynamically switch between bit rate streams of varying quality levels, in order to provide an optimal viewing experience based on a client’s bandwidth and CPU usage.
-
Refers to a web page whose content is generated on-demand by a web application or script.
-
Refers to the mapping of a CNAME record to a directory on a CDN or customer origin server. The purpose of this mapping, which is only used by our CDN, is to establish a user-friendly alias for content served through the CDN. It relies upon your CNAME record being mapped to a CDN hostname via a DNS service provider.
-
This type of URL takes advantage of an edge CNAME configuration and a CNAME record to provide a friendlier alternative to a CDN URL. An edge CNAME URL is specific to the platform from which it was configured.
-
Refers to the portion of the edge CNAME URL that appears after the edge CNAME. It provides the relative path to a folder or an asset on a CDN or customer origin server.
-
This service has been depecreated and should not be applied to your traffic. This feature, which is powered by Google PageSpeed, speeds up your site by optimizing the content being delivered to your users. The most common performance benefits derived from this feature is to decrease the amount of data that needs to be transferred and the number of assets required to properly load a web page.
-
Refers to the protocol (i.e., HTTP and HTTPS) used in a CDN URL or an edge CNAME URL.
-
This type of server is located near the edge of our network where its close proximity to your end-users allows it to deliver data more quickly than normal Internet communication. It is responsible for handling requests and caching assets.
-
Token-Based Authentication requires the use of an encryption key to encrypt and decrypt token values. There are two types of encryption keys, which are a primary and a backup key. Both of these keys can be used to encrypt and decrypt token values.
-
Indicates the capability to redirect all traffic to a backup server/domain when the primary one is deemed unfit to resolve requests.
-
A group that identifies two IP addresses or CNAME records to which our DNS service will resolve requests directed at a CNAME record or subdomain. All requests will resolve to the primary IP address/CNAME. If the primary IP address/CNAME is unavailable, traffic will fail over to the backup IP address/CNAME.
-
Web Application Firewall: A false positive is a legitimate request that was identified as malicioius traffic by Web Application Firewall.
-
Rules Engine: Defines the type of action that will take place when a set of match conditions have been met.
-
A file is the most commonly known example of an asset. Refers to any collection of data that is typically stored as a single unit on a storage unit (e.g., disk drive). An example of an asset that is not physically stored on a disk drive occurs when dynamically generated content is not cached.
-
This service was discontinued on 5/31/2017. The Flash Media Streaming platform streamed live and on-demand content via a Flash media player over a RTMP-based protocol.
-
This service was discontinued on 5/31/2017. The Flash Media Streaming platform streamed live and on-demand content via a Flash media player over a RTMP-based protocol.
-
Identifies cached content that can be served directly by an edge server without requiring revalidation with an origin server. It also indicates that the cached content's TTL has not expired.
-
This type of URL identifies a resource (e.g., asset or file) using the following format: scheme://server/path/resource (e.g., http://cdn.mydomain.com/sales/presentation.pdf).
-
This popular request method is used to retrieve information from a server. A GET request informs the server that the asset at the requested URL should be delivered to the requester.
-
This type of live authentication key may be used to authenticate all live streams for Flash Media Streaming, HLS, or HDS. Only a single global key may be specified.
-
The act of monitoring health status by requiring that a server acknowledge either a HTTP/HTTPS GET/POST, TCP, or TCP SSL request.
-
The DNS Health Checks module checks the health of a server or domain by polling it with an HTTP or TCP request. These health checks are essential when load balancing or failing traffic over multiple servers.
-
This type of record maps a hostname to an IP address. A records are used for IPv4 addresses, while AAAA records are used for IPv6 addresses.
-
Identifies a name that points to a specific host. All of the following are examples of a hostname: cdn.secure.example.com, secure.example.com, and example.com.
-
This platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
-
Refers to the action that will be performed to fulfill an HTTP request. Common HTTP methods for CDN transactions are GET, POST, and HEAD.
-
This method of streaming audio/video content is performed through the HTTP protocol. Progressive downloads are not as secure as other streaming methods, since the entire asset will be stored on your client’s computer. This behavior makes it possible for the requester to save and share your content with other users.
-
Allows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior.
-
Legacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.
-
Refers to a 3 digit code that indicates the status of the HTTP response returned to the requester. Common HTTP status codes are: 200 OK, 304 Not Modified, 404 Not Found, 500 Internal Server Error, and 502 Bad Gateway.
-
A two digit value (e.g., 00 and 80) that identifies how a request will be routed through our CDN.
-
Refers to the process of capturing and transforming encoded media into a stream.
-
Refers to the type of server that is dedicated to the process of capturing and transforming media into a stream. This type of server will then broadcast that stream throughout our CDN.
-
Web Application Firewall: Identifies profiles that may be used to screen production traffic against illegitimate requests.
-
Refers to a whole number (e.g., 1, 2, 3, etc.).
-
Identifies a device (e.g., computer) by a numerical value. This document deals with two versions of IP addresses, which are IPv4/IPv6. Most Internet traffic is routed through IPv4 (e.g., 101.10.10.253). A new version of IP address called IPv6 (e.g., 2001:0db8:85a3:0042:1000:8a2e:0370:7334) is designed to address IPv4 address exhaustion.
-
TCP/IP: Refers to the layer that supports applications and processes. For example, it contains protocols (e.g., HTTP and FTP) that facilitate communication across a network.
-
This type of value does not assign a special meaning to characters. The only exception is % which is used for URL encoding.
-
Authenticates streams before they can be ingested into our network. There are two types of live authentication keys, which are global and stream keys. A live authentication key (e.g., MyStream?MyLiveAuthenticationKey) must be specified when setting an encoder’s stream setting for use with our Flash Media Streaming, HLS, HDS, or DCP solutions.
-
Refers to the streaming of a live event through our Flash Media Streaming platform. This service was discontinued on 5/31/2017.
-
This type of identifier in the CDN URL indicates that requested asset should be streamed from the live ingestion point. A live stream identifier is indicated by "20" as the starting two numbers in the CDN URL path.
-
Instructs all of our POPs to manually cache an asset. This action ensures optimal data delivery performance by immediately serving your content from the edge of our network. It also reduces the traffic sent to the web servers associated with your customer origin configuration.
-
Indicates the capability to distribute requests between multiple web servers or domains.
-
A group that identifies two or more IP addresses/CNAMEs to which our DNS service will resolve requests directed at a CNAME record or subdomain. The weight assigned to each IP address defines the amount of network traffic it will receive.
-
The Managed (Primary) or Secondary DNS module allows DNS zone management, authoritative DNS for zones managed outside of our network, and traffic distribution to multiple servers via load balancing or failover configurations.
-
The Managed (Primary) or Secondary DNS module allows DNS zone management, authoritative DNS for zones managed outside of our network, and traffic distribution to multiple servers via load balancing or failover configurations.
-
Identifies a name server that is authoritative for the zone in question.
-
Identifies one or more master name servers from which the zones identified in a secondary zone group will be transferred. A secondary zone is created for each transferred zone.
-
Rules Engine: Defines a prerequisite that must be met before one or more actions (i.e., features) may be applied to a request.
-
This web application (a.k.a. portal) is designed to administer all CDN-related services. The major features that are available from the MCC are CDN configuration settings, cache management, file management, reports, and analytics. Additionally, the MCC may be used to support organizational business needs, such as granting or denying access to the MCC.
-
This web application (a.k.a. portal) is designed to administer all CDN-related services. The major features that are available from the MCC are CDN configuration settings, cache management, file management, reports, and analytics. Additionally, the MCC may be used to support organizational business needs, such as granting or denying access to the MCC.
-
This service was discontinued on 11/12/2018. This feature dynamically streams content over HTTP. It leverages HTTP/HTTPS for the entire streaming experience from uploading content to playback.
-
Identifies/classifies the data contained in a file.
-
A metric measures the rate, an amount, or the total number of times that a particular attribute occurred over a given record.
-
Identifies/classifies the data contained in a file.
-
A name server, or a domain name server, is a server that can provide an answer to DNS queries according to the information contained within a zone. A single name server can be authoritative for multiple zones. Two types of name servers are authoritative and recursive.
-
A NS record delegates a hostname to a name server.
-
A NS record delegates a hostname to a name server.
-
A file is the most commonly known example of an asset. Refers to any collection of data that is typically stored as a single unit on a storage unit (e.g., disk drive). An example of an asset that is not physically stored on a disk drive occurs when dynamically generated content is not cached.
-
Refers to the streaming of content through our CDN. All of our streaming solutions support this capability.
-
A two digit value (e.g., 00 and 80) that identifies how a request will be routed through our CDN.
-
It references a relative path to a folder or an asset in a CDN URL. This type of path follows the content access point.
-
Refers to the server(s) where content served via the CDN is stored. There are two types of origin servers, which are CDN and customer origin servers. All requests that cannot be fulfilled directly by an edge server are forwarded to an origin server. For example, a request for content that has not been previously cached is forwarded from an edge server to an origin server.
-
This feature provides a layer of protection for a customer origin server by creating an intermediate caching layer between it and our edge servers. This caching layer resides on one or more of our point-of-presence (POPs). Requests that have not been previously cached on a POP will be channelled through the closest origin shield server. The origin shield server will then either serve a cached version of the requested content or retrieve it from a customer origin server. This feature shifts the network load from the customer origin server to the CDN, since most requests will be handled by the origin shield server.
-
Identifies the environment through which your content will be efficiently delivered to your users.
-
A media player uses this type of URL to stream live and on-demand content.
-
A media player uses this type of URL to stream live and on-demand content.
-
Identifies a location on our network through which users can request and receive content.
-
Rules Engine: Refers to a read-only version of a set of rules that identify requests and the set of actions that can be applied to them. A policy may be applied to either the Staging or Production environment.
-
Identifies a location on our network through which users can request and receive content.
-
Instructs all of our POPs to manually cache an asset. This action ensures optimal data delivery performance by immediately serving your content from the edge of our network. It also reduces the traffic sent to the web servers associated with your customer origin configuration.
-
Token-Based Authentication requires the use of an encryption key to encrypt and decrypt token values. There are two types of encryption keys, which are a primary and a backup key. Both of these keys can be used to encrypt and decrypt token values.
-
A zone consists of the portion of the DNS namespace over which authority has been delegated. It contains information (i.e., records) through which an authoritative name server can provide an answer to DNS queries.
-
Refers to the environment responsible for live site (i.e., production) traffic.
-
Refers to requests directed to a live site. For example, the HTTP requests generated when a user visits your web page is considered production traffic.
-
Web Application Firewall: Refers to a configuration that defines the set of security restrictions that may be used to screen inbound HTTP/HTTPS traffic.
-
Refers to the location on the publishing server to which your encoder will broadcast encoded media.
-
A publishing point URL is only used for live streams. An encoder should be configured to push encoded media to this type of URL.
-
Refers to a CDN server that will redistribute encoded media as a streamer that will be broadcast to your end-users via our POPs.
-
Refers to a request to remove a cached version of an asset from all of our edge servers and origin shield servers. A purge can be performed on a folder or an individual asset. One use for this capability is to ensure the delivery of a newer version of that asset.
-
Refers to data that is appended to a URL (e.g., "?Data=xyz" in the following request: http://www.server.com/index.html?Data=xyz). This information may be used in a variety of ways. Our CDN allows each query string variation of a URL to generate a unique cached asset. Additionally, query string information may be stored in our log files.
-
This feature is designed to protect against volumetric attacks and inadvertent DDoS. It is able to do so by controlling the flow of requests to a customer origin server.
-
Delivers near real-time log data to your web server, an AWS S3 bucket, an Azure Block Blob, Splunk Enterprise, Sumo Logic, or Datadog.
-
A DNS zone can contain multiple records. A record defines the set of information through which a name server can provide an answer to a DNS request. We support the following records: A, AAAA, CNAME, MX, NS, SOA, SPF, SRV, and TXT.
-
Identifies a name server that has the capability to cache the answer to a DNS query provided by an authoritative name server.
-
This type of value is interpreted as a regular expression that defines a pattern of characters.
-
This feature generates and delivers custom reports.
-
Refers to the request from a client to a server for an asset. A request consists of a set of headers and a body sent from a client. Header data and the body define the requested content. A request for CDN content must be performed using a CDN or edge CNAME URL. This type of request is sent from a client to an edge server. If the requested content is not found, then our edge servers will forward this request to an origin server.
-
Identifies the set of data sent from the requester. The most common usage of a request body for CDN traffic occurs with POST requests.
-
This type of header describes a client's request for content.
-
Indicates the type of action that a server should perform on the asset identified in the request URL. Common HTTP request methods are GET, POST, PUT, DELETE, HEAD, OPTIONS, TRACE, and CONNECT.
-
Refers to the user that requested content.
-
A file is the most commonly known example of an asset. Refers to any collection of data that is typically stored as a single unit on a storage unit (e.g., disk drive). An example of an asset that is not physically stored on a disk drive occurs when dynamically generated content is not cached.
-
Consists of the headers and the body sent from a server responding to a request. If an origin server is returning a response, then this response will be sent to an edge server. The edge server will then forward the response to a client.
-
Identifies the set of data that was requested. This data typically consists of a file.
-
This type of header describes the HTTP response provided by a server. Among their many uses, certain response headers may be used to define the cache policy for the requested content.
-
Refers to the process that occurs when a request for stale content requires that our edge servers check for a new version of the requested content on the origin server.
-
Cache revalidation is the process through which an edge server checks the origin server for a newer version of a cached asset. Revalidation is triggered when the TTL for the requested content has expired.
-
Identifies a name server that can return the authoritative name server for each top-level domain.
-
This platform is designed to provide reliable, high performance, and secure DNS service. This DNS service consists of zone administration, traffic management, and custom routing policies.
-
Rules Engine: Refers to a set of statements that identify a set of requests and the manner in which those requests will be handled.
-
Allows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior.
-
For the purpose of HTTP traffic, it identifies whether traffic should use the HTTP or HTTPS protocol. The syntax for a URL scheme consists of the protocol, a colon, and two forward slashes (e.g., http:// or https://).
-
The Managed (Primary) or Secondary DNS module allows DNS zone management, authoritative DNS for zones managed outside of our network, and traffic distribution to multiple servers via load balancing or failover configurations.
-
Identifies a zone that is a copy of a zone that is managed outside of our network. This type of zone is automatically synchronized to match any changes performed to the source zone. Our DNS service is authoritative for all secondary zones.
-
Identifies one or more zones managed outside of our network. A secondary zone will be generated for each zone defined in a secondary zone group.
-
This feature allows dynamic streaming for live and on-demand content over the HTTP Large platform to Silverlight players. Our live streaming solution may be transmuxed to provide support for iOS devices.
-
This environment provides a sandbox for testing a CDN setup. One use for this environment is to test out a new policy before applying it to live site traffic.
-
Identifies cached content whose TTL has expired. Our edge servers revalidate stale content with the origin server. This step ensures that the latest version of the requested content is served to the requester.
-
Rules Engine: Refers to the set of conditional expressions & conditions that identify a single type of request. The last conditional expression in a statement should contain a set of actions that will be applied to that request type.
-
Refers to content that is served without being modified or generated. The response matches the file stored on the origin server.
-
Consists of the delivery of audio/video content in a format that allows your clients to play it back through a multimedia player.
-
This type of Live Authentication key can only authenticate a live stream when it is published to the path associated with it.
-
Refers to one or more numbers, characters, and/or symbols.
-
Refers to content linked from within the requested asset. For example, a web page may contain src and href links to CSS, JS, and images. The context for this term typically revolves around Edge Optimizer processing.
-
Refers to content linked from within the requested asset. For example, a web page may contain src and href links to CSS, JS, and images. The context for this term typically revolves around Edge Optimizer processing.
-
Identifies a domain as a part of a larger domain. This relationship is explored for a sample domain called "us.mydomain.com." "us.mydomain.com" is a subdomain of the "mydomain.com" domain. Both "us.mydomain.com" and "mydomain.com" are considered to be domains as well. Each domain, with the exception of the top-level domain (e.g., .com), is a subdomain as well as a domain.
-
The Token-Based Authentication feature enforces authentication prior to content delivery. Authentication takes place via an encoded token value that must be included in the request URL. This token value is then decrypted on an edge server. The requested content will only be delivered when the user meets the requirement(s) defined in the token.
-
Time to Live. Refers to the amount of time that a cached asset is still considered fresh. Our edge servers will continue to serve a cached version of an asset while its TTL has not expired. An asset's TTL is calculated by the Cache-Control and Expires headers associated with the response sent by the origin server.
-
Transport Layer Security. Refers to a protocol that encrypts traffic for the purpose of delivery over HTTPS. TLS is the successor to SSL.
-
Refers to a certificate that allows you to use the TLS protocol to encrypt traffic between the client and our network for the purpose of delivery over HTTPS.
-
A token value must be provided when Token-Based Authentication has been applied to the requested content. Each token value contains a set of encoded requirements that must be met before content delivery may take place. A token value may be specified as a query string in the request URL (e.g., sales.pdf?1234567890AB).
-
The Token-Based Authentication feature enforces authentication prior to content delivery. Authentication takes place via an encoded token value that must be included in the request URL. This token value is then decrypted on an edge server. The requested content will only be delivered when the user meets the requirement(s) defined in the token.
-
Refers to the process of changing the multimedia container while retaining its content (i.e., audio/video).
-
Transaction Signature. Our Route solution allows the use of TSIG to provide a cryptographically secure method through which zone transfers may take place between a master and slave name server.
-
Time to Live. Refers to the amount of time that a cached asset is still considered fresh. Our edge servers will continue to serve a cached version of an asset while its TTL has not expired. An asset's TTL is calculated by the Cache-Control and Expires headers associated with the response sent by the origin server.
-
Refers to the portion of the URL that appears directly after the hostname. It provides the relative path to a specific folder or asset.
-
For the purpose of HTTP traffic, it identifies whether traffic should use the HTTP or HTTPS protocol. The syntax for a URL scheme consists of the protocol, a colon, and two forward slashes (e.g., http:// or https://).
-
Refers to software that acts on behalf of a user. For example, a web browser (e.g., FireFox, Chrome, and Internet Explorer) is a user agent. A web browser will make HTTP/HTTPS requests based on user actions (e.g., requesting a web site or clicking a link).
-
Identifies a name server that leverages your zone name. This lends a professional appearance to a site's DNS.
-
Video On-Demand. Allows the playback of previously encoded content. One use for VOD is to allow viewers to stream your content at any time.
-
Video On-Demand. Allows the playback of previously encoded content. One use for VOD is to allow viewers to stream your content at any time.
-
Web Application Firewall is designed to secure site traffic against DDoS and application layer attacks. It also filters unwanted traffic by enforcing a custom delivery profile and whitelists, access list, and blacklists. Finally, it controls the flow of requests to your applications.
-
Web Application Firewall (Legacy) is designed to secure site traffic against DDoS and application layer attacks. It also filters unwanted traffic by enforcing a custom delivery profile and whitelists/blacklists.
-
WAF Essential (Legacy) provides basic protection against DDoS, application layer attacks, and volumetric attacks. Consider using WAF for a more robust solution.
-
Web Application Firewall is designed to secure site traffic against DDoS and application layer attacks. It also filters unwanted traffic by enforcing a custom delivery profile and whitelists, access list, and blacklists. Finally, it controls the flow of requests to your applications.
-
Web Application Firewall (Legacy) is designed to secure site traffic against DDoS and application layer attacks. It also filters unwanted traffic by enforcing a custom delivery profile and whitelists/blacklists.
-
Indicates the capability to distribute requests between multiple web servers or domains.
-
A group that identifies two or more IP addresses/CNAMEs to which our DNS service will resolve requests directed at a CNAME record or subdomain. The weight assigned to each IP address defines the amount of network traffic it will receive.
-
This type of value supports the use of special characters to establish a pattern. For example, specifying an asterisk within this type of value will match one or more characters.
-
The purpose of ScientiaMobile's Wireless Universal Resource FiLe is to detect mobile devices. HTTP Rules Engine leverages their comprehensive database to allow custom logic to be defined around how mobile devices are handled.
-
A zone consists of the portion of the DNS namespace over which authority has been delegated. It contains information (i.e., records) through which an authoritative name server can provide an answer to DNS queries.