Restricting Access by Protocol

Applies To:

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

HTTP SmallLegacy. 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.

ADNThe 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.

TBAThe 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.

You can choose to allow or block users depending on the protocol used to request the desired content. The parameter used to allow access by protocol is called "ec_proto_allow," while the one that is used to deny access by protocol is called "ec_proto_deny." The only valid values for these parameters are "http" and "https." You can choose to allow or deny both parameters by setting the desired parameter to "http,https."

Keep in mind that the values specified for this parameter are case-sensitive. Make sure to specify the protocol in lower-case letters (e.g., http or https).

Although a typical configuration should not include both parameters, it is possible for a token to contain both of these requirements. In such a case, the ec_proto_allow parameter takes precedence over the ec_proto_deny parameter.