Merge pull request #296487 from Harikrishnan-M-B/patch-30

removed edgio content

Author: ttorble

articles/cdn/cdn-cors.md

@@ -55,39 +55,3 @@ A complex request is a CORS request where the browser is required to send a *pre
 CORS on Azure CDN works automatically without extra configurations when the **Access-Control-Allow-Origin** header is set to wildcard (*) or a single origin. CDN cache the first response and subsequent requests use the same header.
 
 If requests have already been made to the CDN prior to CORS being set on your origin, you need to purge content on your endpoint content to reload the content with the **Access-Control-Allow-Origin** header.
-
-## Multiple origin scenarios
-
-If you need to allow a specific list of origins to be allowed for CORS, things get a little more complicated. The problem occurs when the CDN caches the **Access-Control-Allow-Origin** header for the first CORS origin. When a different CORS origin makes a subsequent request, the CDN serves the cached **Access-Control-Allow-Origin** header, which doesn't match. There are several ways to correct this problem.
-
-### Azure CDN standard profiles
-
-On Azure CDN Standard from Microsoft, you can create a rule in the [Standard rules engine](cdn-standard-rules-engine-reference.md) to check the **Origin** header on the request. If it's a valid origin, your rule set the **Access-Control-Allow-Origin** header with the desired value. In this case, the **Access-Control-Allow-Origin** header from the file's origin server is ignored and the CDN's rules engine completely manages the allowed CORS origins.
-
-![Rules example with standard rules engine](./media/cdn-cors/cdn-standard-cors.png)
-
-> [!TIP]
-> You can add additional actions to your rule to modify additional response headers, such as **Access-Control-Allow-Methods**.
->
-
-#### One regular expression with all valid origins
-
-In this case, you create a regular expression that includes all of the origins you want to allow:
-
-```http
-https?:\/\/(www\.contoso\.com|contoso\.com|www\.microsoft\.com|microsoft.com\.com)$
-```
-
-If the regular expression matches, your rule replaces the **Access-Control-Allow-Origin** header (if any) from the origin with the origin that sent the request. You can also add extra CORS headers, such as **Access-Control-Allow-Methods**.
-
-![Rules example with regular expression](./media/cdn-cors/cdn-cors-regex.png)
-
-#### Request header rule for each origin.
-
-Rather than regular expressions, you can instead create a separate rule for each origin you wish to allow using the **Request Header Wildcard** [match condition](./cdn-verizon-premium-rules-engine-reference-match-conditions.md). As with the regular expression method, the rules engine alone sets the CORS headers.
-
-![Rules example without regular expression](./media/cdn-cors/cdn-cors-no-regex.png)
-
-> [!TIP]
-> In the example, the use of the wildcard character * tells the rules engine to match both HTTP and HTTPS.
->