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/frontdoor/front-door-faq.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -49,9 +49,9 @@ sections:
49
49
- question: |
50
50
Can I deploy another CDN from an external vendor behind or in front of Front Door?
51
51
answer: |
52
-
Chaining two CDNs is a generally not a recommended approach, it would work but comes with the following cons
52
+
Chaining two CDNs is generally not a recommended approach, it would work but comes with the following cons
53
53
1. CDN’s last mile acceleration utilizes keeping the connection stream with the origin, and finding optimal path to the origin to achieve best results. Chaining two CDNs together typically negates some of the benefits from last mile acceleration.
54
-
2. Security controls become less effective at the second CDN. Any client IP based ACLing will not work at the second CDN as the second CDN will see thw first CDN’s exit node as Client IPs. Content payload will still be inspected.
54
+
2. Security controls become less effective at the second CDN. Any client IP based ACLing will not work at the second CDN as the second CDN will see the first CDN’s exit node as Client IPs. Content payload will still be inspected.
55
55
3. Many organizations can’t handle the complexity of troubleshooting two CDNs being chained and when a problem it becomes hard to figure out which CDN is having the issue.
0 commit comments