You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cdn/cdn-http-debug-headers.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ The debug cache request header, `X-EC-Debug`, provides additional information ab
23
23
## Usage
24
24
The response sent from the POP servers to a user includes the `X-EC-Debug` header only when the following conditions are met:
25
25
26
-
- The [Debug Cache Response Headers feature](cdn-rules-engine-reference-features.md#debug-cache-response-headers) has been enabled on the rules engine for the specified request.
26
+
- The [Debug Cache Response Headers feature](cdn-verizon-premium-rules-engine-reference-features.md#debug-cache-response-headers) has been enabled on the rules engine for the specified request.
27
27
- The specified request defines the set of debug cache response headers that will be included in the response.
28
28
29
29
## Requesting debug cache information
@@ -147,7 +147,7 @@ The terms used in the above response header syntax are defined as follows:
147
147
148
148
- MATimePeriod: Converts the max-age value (that is, MASeconds) to the approximate equivalent of a larger unit (for example, days).
149
149
150
-
- UnixTime: Indicates the cache timestamp of the requested content in Unix time (a.k.a. POSIX time or Unix epoch). The cache timestamp indicates the starting date/time from which an asset's TTL will be calculated.
150
+
- UnixTime: Indicates the cache timestamp of the requested content in Unix time (also known as POSIX time or Unix epoch). The cache timestamp indicates the starting date/time from which an asset's TTL will be calculated.
151
151
152
152
If the origin server does not utilize a third-party HTTP caching server or if that server does not return the Age response header, then the cache timestamp will always be the date/time when the asset was retrieved or revalidated. Otherwise, the POP servers will use the Age field to calculate the asset's TTL as follows: Retrieval/RevalidateDateTime - Age.
Copy file name to clipboardExpand all lines: articles/cdn/cdn-http-variables.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,11 +21,11 @@ ms.author: magattus
21
21
# HTTP variables for Azure CDN rules engine
22
22
HTTP variables provide the means through which you can retrieve HTTP request and response metadata. This metadata can then be used to dynamically alter a request or a response. The use of HTTP variables is restricted to the following rules engine features:
The following table describes the supported HTTP variables. A blank value is returned when GEO metadata (for example, postal code) is unavailable for a particular request.
@@ -110,7 +110,7 @@ The following table describes circumstances under which the specified text isn't
110
110
| Condition | Description | Example |
111
111
| --------- | ----------- | --------|
112
112
| Escaping % symbol | The percentage symbol can be escaped through the use of a backslash. <br />The sample value to the right will be treated as a literal value and not as an HTTP variable.|\%{host} |
113
-
| Unknown variables | An empty string is always returned for unknown variables. | %{unknownvariable} |
113
+
| Unknown variables | An empty string is always returned for unknown variables. | %{unknown_variable} |
114
114
| Invalid characters or syntax | Variables that contain invalid characters or syntax are treated as literal values. <br /><br />Example #1: The specified value contains an invalid character (for example, -). <br /><br />Example #2: The specified value contains a double set of curly braces. <br /><br />Example #3: The specified value is missing a closing curly brace.<br /> | Example #1: %{resp_user-agent} <br /><br />Example #2: %{{host}} <br /><br />Example #3: %{host |
115
115
| Missing variable name | A NULL value is always returned when a variable is not specified. | %{} |
116
116
| Trailing characters | Characters that trail a variable are treated as literal values. <br />The sample value to the right contains a trailing curly brace that will be treated as a literal value. | %{host}} |
@@ -124,9 +124,9 @@ The following table describes how to define a default value.
124
124
125
125
| Condition | Syntax | Example | Description |
126
126
| --------- | ------ | --------| ----------- |
127
-
| Set a header to a default value when it meets any of the following conditions: <br /><br />- Missing Header <br /><br />- Header value is set to NULL.| %{Variable:=Value} | %{http_referer:=unspecified} | The Referer header will only be set to *unspecified* when it is either missing or set to NULL. No action will take place if it has been set. |
128
-
| Set a header to a default value when it is missing. | %{Variable=Value} | %{http_referer=unspecified} | The Referer header will only be set to *unspecified* when it is missing. No action will take place if it has been set. |
129
-
| Set the header to a default value when it does not meet any of the following conditions: <br /><br />- Missing<br /><br /> - Set to NULL. | %{Variable:+Value} | %{http_referer:+unspecified} | The Referer header will only be set to *unspecified* when a value has been assigned to it. No action will take place if it is either missing or set to NULL. |
127
+
| Set a header to a default value when it meets any of the following conditions: <br /><br />- Missing Header <br /><br />- Header value is set to NULL.| %{Variable:=Value} | %{http_referrer:=unspecified} | The Referrer header will only be set to *unspecified* when it is either missing or set to NULL. No action will take place if it has been set. |
128
+
| Set a header to a default value when it is missing. | %{Variable=Value} | %{http_referrer=unspecified} | The Referrer header will only be set to *unspecified* when it is missing. No action will take place if it has been set. |
129
+
| Set the header to a default value when it does not meet any of the following conditions: <br /><br />- Missing<br /><br /> - Set to NULL. | %{Variable:+Value} | %{http_referrer:+unspecified} | The Referrer header will only be set to *unspecified* when a value has been assigned to it. No action will take place if it is either missing or set to NULL. |
130
130
131
131
## Manipulating variables
132
132
Variables can be manipulated in the following ways:
Copy file name to clipboardExpand all lines: articles/cdn/cdn-storage-custom-domain-https.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Azure CDN ignores any restrictions added to the SAS token. For example, all SAS
41
41
If you create multiple SAS URLs for the same blob endpoint, consider enabling query string caching. Doing so ensures that each URL is treated as a unique entity. For more information, see [Controlling Azure CDN caching behavior with query strings](cdn-query-string.md).
42
42
43
43
## HTTP-to-HTTPS redirection
44
-
You can elect to redirect HTTP traffic to HTTPS by creating a [URL Redirect rule](cdn-rules-engine-reference-features.md#url-redirect) with the [Azure CDN rules engine](cdn-rules-engine.md). This option requires an **Azure CDN Premium from Verizon** profile.
44
+
You can elect to redirect HTTP traffic to HTTPS by creating a [URL Redirect rule](cdn-verizon-premium-rules-engine-reference-features.md#url-redirect) with the [Azure CDN rules engine](cdn-verizon-premium-rules-engine.md). This option requires an **Azure CDN Premium from Verizon** profile.
Copy file name to clipboardExpand all lines: articles/cdn/cdn-token-auth.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -176,17 +176,17 @@ The following flowchart describes how Azure CDN validates a client request when
176
176
3. Under **HTTP Large**, select **Rules Engine**. You use the rules engine to define paths to apply the feature, enable the token authentication feature, and enable additional token authentication-related capabilities. For more information, see [Rules engine reference](cdn-rules-engine-reference.md).
177
177
178
178
1. Select an existing rule or create a new rule to define the asset or path for which you want to apply token authentication.
179
-
2. To enable token authentication on a rule, select **[Token Auth](cdn-rules-engine-reference-features.md#token-auth)** from the **Features** list, then select **Enabled**. Select **Update** if you are updating a rule or **Add** if you are creating a rule.
179
+
2. To enable token authentication on a rule, select **[Token Auth](cdn-verizon-premium-rules-engine-reference-features.md#token-auth)** from the **Features** list, then select **Enabled**. Select **Update** if you are updating a rule or **Add** if you are creating a rule.
4. In the rules engine, you can also enable additional token authentication-related features. To enable any of the following features, select it from the **Features** list, then select **Enabled**.
184
184
185
-
-**[Token Auth Denial Code](cdn-rules-engine-reference-features.md#token-auth-denial-code)**: Determines the type of response that is returned to a user when a request is denied. Rules set here override the response code set in the **Custom Denial Handling** section on the token-based authentication page.
185
+
-**[Token Auth Denial Code](cdn-verizon-premium-rules-engine-reference-features.md#token-auth-denial-code)**: Determines the type of response that is returned to a user when a request is denied. Rules set here override the response code set in the **Custom Denial Handling** section on the token-based authentication page.
186
186
187
-
-**[Token Auth Ignore URL Case](cdn-rules-engine-reference-features.md#token-auth-ignore-url-case)**: Determines whether the URL used to validate the token is case-sensitive.
187
+
-**[Token Auth Ignore URL Case](cdn-verizon-premium-rules-engine-reference-features.md#token-auth-ignore-url-case)**: Determines whether the URL used to validate the token is case-sensitive.
188
188
189
-
-**[Token Auth Parameter](cdn-rules-engine-reference-features.md#token-auth-parameter)**: Renames the token auth query string parameter that appears in the requested URL.
189
+
-**[Token Auth Parameter](cdn-verizon-premium-rules-engine-reference-features.md#token-auth-parameter)**: Renames the token auth query string parameter that appears in the requested URL.
Copy file name to clipboardExpand all lines: articles/cdn/cdn-verizon-http-headers.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ ms.author: magattus
22
22
23
23
For **Azure CDN Premium from Verizon** products, when an HTTP request is sent to the origin server, the point-of-presence (POP) server can add one or more reserved headers (or proxy special headers) in the client request to the POP. These headers are in addition to the standard forwarding headers received. For information about standard request headers, see [Request fields](https://en.wikipedia.org/wiki/List_of_HTTP_header_fields#Request_fields).
24
24
25
-
If you want to prevent one of these reserved headers from being added in the Azure CDN (Content Delivery Network) POP request to the origin server, you must create a rule with the [Proxy Special Headers feature](cdn-rules-engine-reference-features.md#proxy-special-headers) in the rules engine. In this rule, exclude the header you want to remove from the default list of headers in the headers field. If you've enabled the [Debug Cache Response Headers feature](cdn-rules-engine-reference-features.md#debug-cache-response-headers), be sure to add the necessary `X-EC-Debug` headers.
25
+
If you want to prevent one of these reserved headers from being added in the Azure CDN (Content Delivery Network) POP request to the origin server, you must create a rule with the [Proxy Special Headers feature](cdn-verizon-premium-rules-engine-reference-features.md#proxy-special-headers) in the rules engine. In this rule, exclude the header you want to remove from the default list of headers in the headers field. If you've enabled the [Debug Cache Response Headers feature](cdn-verizon-premium-rules-engine-reference-features.md#debug-cache-response-headers), be sure to add the necessary `X-EC-Debug` headers.
26
26
27
27
For example, to remove the `Via` header, the headers field of the rule should include the following list of headers: *X-Forwarded-For, X-Forwarded-Proto, X-Host, X-Midgress, X-Gateway-List, X-EC-Name, Host*.
title: Azure CDN rules engine conditional expressions | Microsoft Docs
3
-
description: Reference documentation for Azure CDN rules engine match conditions and features.
2
+
title: Azure CDN from Verizon Premium rules engine conditional expressions | Microsoft Docs
3
+
description: Reference documentation for Azure CDN from Verizon Premium rules engine match conditions and features.
4
4
services: cdn
5
-
documentationcenter: ''
6
-
author: Lichard
7
-
manager: akucer
8
-
editor: ''
5
+
author: mdgattuso
9
6
10
-
ms.assetid: 669ef140-a6dd-4b62-9b9d-3f375a14215e
11
7
ms.service: cdn
12
-
ms.workload: media
13
-
ms.tgt_pltfrm: na
14
-
ms.devlang: na
15
8
ms.topic: article
16
-
ms.date: 01/23/2017
17
-
ms.author: rli
9
+
ms.date: 05/31/2019
10
+
ms.author: magattus
18
11
19
12
---
20
13
21
-
# Azure CDN rules engine conditional expressions
22
-
This topic lists detailed descriptions of the Conditional Expressions for Azure Content Delivery Network (CDN) [Rules Engine](cdn-rules-engine.md).
14
+
# Azure CDN from Verizon Premium rules engine conditional expressions
15
+
16
+
This article lists detailed descriptions of the Conditional Expressions for Azure Content Delivery Network (CDN) [Rules Engine](cdn-verizon-premium-rules-engine.md).
23
17
24
18
The first part of a rule is the Conditional Expression.
25
19
26
20
Conditional Expression | Description
27
21
-----------------------|-------------
28
-
IF | An IF expression is always a part of the first statement in a rule. Like all other conditional expressions, this IF statement must be associated with a match. If no additional conditional expressions are defined, then this match determines the criterion that must be met before a set of features may be applied to a request.
22
+
IF | An IF expression is always a part of the first statement in a rule. Like all other conditional expressions, this IF statement must be associated with a match. If no additional conditional expressions are defined, this match determines the criterion that must be met before a set of features may be applied to a request.
29
23
AND IF | An AND IF expression may only be added after the following types of conditional expressions:IF,AND IF. It indicates that there is another condition that must be met for the initial IF statement.
30
24
ELSE IF| An ELSE IF expression specifies an alternative condition that must be met before a set of features specific to this ELSE IF statement takes place. The presence of an ELSE IF statement indicates the end of the previous statement. The only conditional expression that may be placed after an ELSE IF statement is another ELSE IF statement. This means that an ELSE IF statement may only be used to specify a single additional condition that has to be met.
31
25
32
26
**Example**:
33
27
34
28
35
29
> [!TIP]
36
-
> A subsequent rule may override the actions specified by a previous rule.
30
+
> A subsequent rule may override the actions specified by a previous rule.
37
31
> Example: A catch-all rule secures all requests via Token-Based Authentication. Another rule may be created directly below it to make an exception for certain types of requests.
0 commit comments