Skip to content

Commit 174bc45

Browse files
Merge pull request #116453 from KumudD/cdnupdatemay20
CDN updates
2 parents e004aec + e142d2a commit 174bc45

File tree

5 files changed

+58
-1191
lines changed

5 files changed

+58
-1191
lines changed

articles/cdn/cdn-verizon-premium-rules-engine-reference-features.md

Lines changed: 5 additions & 149 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: asudbring
66

77
ms.service: azure-cdn
88
ms.topic: article
9-
ms.date: 05/31/2019
9+
ms.date: 05/26/2020
1010
ms.author: allensu
1111

1212
---
@@ -17,150 +17,9 @@ This article lists detailed descriptions of the available features for Azure Con
1717

1818
The third part of a rule is the feature. A feature defines the type of action that is applied to the request type that is identified by a set of match conditions.
1919

20-
## Access features
21-
22-
These features are designed to control access to content.
23-
24-
Name | Purpose
25-
-----|--------
26-
[Deny Access (403)](#deny-access-403) | Determines whether all requests are rejected with a 403 Forbidden response.
27-
[Token Auth](#token-auth) | Determines whether Token-Based Authentication is applied to a request.
28-
[Token Auth Denial Code](#token-auth-denial-code) | Determines the type of response that is returned to a user when a request is denied due to token-based authentication.
29-
[Token Auth Ignore URL Case](#token-auth-ignore-url-case) | Determines whether URL comparisons made by Token-Based Authentication are case-sensitive.
30-
[Token Auth Parameter](#token-auth-parameter) | Determines whether the Token-Based Authentication query string parameter should be renamed.
31-
32-
## Caching features
33-
34-
These features are designed to customize when and how content is cached.
35-
36-
Name | Purpose
37-
-----|--------
38-
[Bandwidth Parameters](#bandwidth-parameters) | Determines whether bandwidth throttling parameters (for example, ec_rate and ec_prebuf) are active.
39-
[Bandwidth Throttling](#bandwidth-throttling) | Throttles the bandwidth for the response provided by the point-of-presence (POP).
40-
[Bypass Cache](#bypass-cache) | Determines whether the request should bypass caching.
41-
[Cache-Control Header Treatment](#cache-control-header-treatment) | Controls the generation of `Cache-Control` headers by the POP when External Max-Age feature is active.
42-
[Cache-Key Query String](#cache-key-query-string) | Determines whether the cache-key includes or excludes query string parameters associated with a request.
43-
[Cache-Key Rewrite](#cache-key-rewrite) | Rewrites the cache-key associated with a request.
44-
[Complete Cache Fill](#complete-cache-fill) | Determines what happens when a request results in a partial cache miss on a POP.
45-
[Compress File Types](#compress-file-types) | Defines the file formats for the files that are compressed on the server.
46-
[Default Internal Max-Age](#default-internal-max-age) | Determines the default max-age interval for POP to origin server cache revalidation.
47-
[Expires Header Treatment](#expires-header-treatment) | Controls the generation of `Expires` headers by a POP when the External Max-Age feature is active.
48-
[External Max-Age](#external-max-age) | Determines the max-age interval for browser to POP cache revalidation.
49-
[Force Internal Max-Age](#force-internal-max-age) | Determines the max-age interval for POP to origin server cache revalidation.
50-
[H.264 Support (HTTP Progressive Download)](#h264-support-http-progressive-download) | Determines the types of H.264 file formats that may be used to stream content.
51-
[Honor No-Cache Request](#honor-no-cache-request) | Determines whether an HTTP client's no-cache requests are forwarded to the origin server.
52-
[Ignore Origin No-Cache](#ignore-origin-no-cache) | Determines whether the CDN ignores certain directives served from an origin server.
53-
[Ignore Unsatisfiable Ranges](#ignore-unsatisfiable-ranges) | Determines the response that is returned to clients when a request generates a 416 Requested Range Not Satisfiable status code.
54-
[Internal Max-Stale](#internal-max-stale) | Controls how long past the normal expiration time a cached asset may be served from a POP when the POP is unable to revalidate the cached asset with the origin server.
55-
[Partial Cache Sharing](#partial-cache-sharing) | Determines whether a request can generate partially cached content.
56-
[Prevalidate Cached Content](#prevalidate-cached-content) | Determines whether cached content is eligible for early revalidation before its TTL expires.
57-
[Refresh Zero-Byte Cache Files](#refresh-zero-byte-cache-files) | Determines how an HTTP client's request for a 0-byte cache asset is handled by the POPs.
58-
[Set Cacheable Status Codes](#set-cacheable-status-codes) | Defines the set of status codes that can result in cached content.
59-
[Stale Content Delivery on Error](#stale-content-delivery-on-error) | Determines whether expired cached content is delivered when an error occurs during cache revalidation or when retrieving the requested content from the customer origin server.
60-
[Stale While Revalidate](#stale-while-revalidate) | Improves performance by allowing the POPs to serve stale client to the requester while revalidation takes place.
61-
62-
## Comment feature
63-
64-
This feature is designed to provide additional information within a rule.
65-
66-
Name | Purpose
67-
-----|--------
68-
[Comment](#comment) | Allows a note to be added within a rule.
69-
70-
## Header features
71-
72-
These features are designed to add, modify, or delete headers from the request or response.
73-
74-
Name | Purpose
75-
-----|--------
76-
[Age Response Header](#age-response-header) | Determines whether an Age response header is included in the response sent to the requester.
77-
[Debug Cache Response Headers](#debug-cache-response-headers) | Determines whether a response may include the X-EC-Debug response header, which provides information on the cache policy for the requested asset.
78-
[Modify Client Request Header](#modify-client-request-header) | Overwrites, appends, or deletes a header from a request.
79-
[Modify Client Response Header](#modify-client-response-header) | Overwrites, appends, or deletes a header from a response.
80-
[Set Client IP Custom Header](#set-client-ip-custom-header) | Allows the IP address of the requesting client to be added to the request as a custom request header.
81-
82-
## Logging features
83-
84-
These features are designed to customize the data stored in raw log files.
85-
86-
Name | Purpose
87-
-----|--------
88-
[Custom Log Field 1](#custom-log-field-1) | Determines the format and the content that is assigned to the custom log field in a raw log file.
89-
[Log Query String](#log-query-string) | Determines whether a query string is stored along with the URL in access logs.
9020

21+
For the most recent features, see the [Verizon Rules Engine documentation](https://docs.vdms.com/cdn/index.html#Quick_References/HRE_QR.htm#Actions).
9122

92-
<!---
93-
## Optimize
94-
95-
These features determine whether a request will undergo the optimizations provided by Edge Optimizer.
96-
97-
Name | Purpose
98-
-----|--------
99-
Edge Optimizer | Determines whether Edge Optimizer can be applied to a request.
100-
Edge Optimizer – Instantiate Configuration | Instantiates or activates the Edge Optimizer configuration associated with a site.
101-
102-
### Edge Optimizer
103-
**Purpose:** Determines whether Edge Optimizer can be applied to a request.
104-
105-
If this feature has been enabled, then the following criteria must also be met before the request will be processed by Edge Optimizer:
106-
107-
- The requested content must use an edge CNAME URL.
108-
- The edge CNAME referenced in the URL must correspond to a site whose configuration has been activated in a rule.
109-
110-
This feature requires the ADN platform and the Edge Optimizer feature.
111-
112-
Value|Result
113-
-|-
114-
Enabled|Indicates that the request is eligible for Edge Optimizer processing.
115-
Disabled|Restores the default behavior. The default behavior is to deliver content over the ADN platform without any additional processing.
116-
117-
**Default Behavior:** Disabled
118-
119-
120-
### Edge Optimizer - Instantiate Configuration
121-
**Purpose:** Instantiates or activates the Edge Optimizer configuration associated with a site.
122-
123-
This feature requires the ADN platform and the Edge Optimizer feature.
124-
125-
Key information:
126-
127-
- Instantiation of a site configuration is required before requests to the corresponding edge CNAME can be processed by Edge Optimizer.
128-
- This instantiation only needs to be performed a single time per site configuration. A site configuration that has been instantiated will remain in that state until the Edge Optimizer – Instantiate Configuration feature that references it is removed from the rule.
129-
- The instantiation of a site configuration does not mean that all requests to the corresponding edge CNAME will automatically be processed by Edge Optimizer. The Edge Optimizer feature determines whether an individual request will be processed.
130-
131-
If the desired site does not appear in the list, then you should edit its configuration and verify that the Active option has been marked.
132-
133-
**Default Behavior:** Site configurations are inactive by default.
134-
--->
135-
136-
## Origin features
137-
138-
These features are designed to control how the CDN communicates with an origin server.
139-
140-
Name | Purpose
141-
-----|--------
142-
[Maximum Keep-Alive Requests](#maximum-keep-alive-requests) | Defines the maximum number of requests for a Keep-Alive connection before it is closed.
143-
[Proxy Special Headers](#proxy-special-headers) | Defines the set of CDN-specific request headers that are forwarded from a POP to an origin server.
144-
145-
## Specialty features
146-
147-
These features provide advanced functionality for advanced users.
148-
149-
Name | Purpose
150-
-----|--------
151-
[Cacheable HTTP Methods](#cacheable-http-methods) | Determines the set of additional HTTP methods that can be cached on the network.
152-
[Cacheable Request Body Size](#cacheable-request-body-size) | Defines the threshold for determining whether a POST response can be cached.
153-
[User Variable](#user-variable) | For internal use only.
154-
155-
## URL features
156-
157-
These features allow a request to be redirected or rewritten to a different URL.
158-
159-
Name | Purpose
160-
-----|--------
161-
[Follow Redirects](#follow-redirects) | Determines whether requests can be redirected to the hostname defined in the Location header returned by a customer origin server.
162-
[URL Redirect](#url-redirect) | Redirects requests via the Location header.
163-
[URL Rewrite](#url-rewrite) | Rewrites the request URL.
16423

16524
## Azure CDN from Verizon Premium rules engine features reference
16625

@@ -484,8 +343,8 @@ Internet Media Type|Description
484343
text/plain|Plain text files
485344
text/html| HTML files
486345
text/css|Cascading Style Sheets (CSS)
487-
application/x-javascript|Javascript
488-
application/javascript|Javascript
346+
application/x-javascript|JavaScript
347+
application/javascript|JavaScript
489348

490349
Key information:
491350

@@ -1421,13 +1280,10 @@ This feature includes matching criteria that must be met before it can be applie
14211280
**Purpose:** For internal use only.
14221281

14231282
[Back to top](#azure-cdn-from-verizon-premium-rules-engine-features)
1424-
1425-
</br>
1426-
14271283
## Next steps
14281284

14291285
- [Rules engine reference](cdn-verizon-premium-rules-engine-reference.md)
14301286
- [Rules engine conditional expressions](cdn-verizon-premium-rules-engine-reference-conditional-expressions.md)
14311287
- [Rules engine match conditions](cdn-verizon-premium-rules-engine-reference-match-conditions.md)
14321288
- [Override HTTP behavior using the rules engine](cdn-verizon-premium-rules-engine.md)
1433-
- [Azure CDN overview](cdn-overview.md)
1289+
- [Azure CDN overview](cdn-overview.md)

0 commit comments

Comments
 (0)