Add an acl
Use access control lists (ACLs) to limit access to your site based on a client's IP address, geographic location, autonomous system number (ASN), or use of anonymizer. You can define ACLs at both the host and path levels. Host ACL settings are inherited by paths, unless a path has its own ACL settings. In that case, path ACL settings override the host ACL settings.
When defining an ACL, you consider whether the host or path Default Access setting is Allow All or Deny All. Then you define the ACL rules that specify the exceptions. For example, if the Default Access setting is Allow All, the ACL rules specify which IP addresses to deny. If the Default Access setting is Deny All, the ACL rules specify which IP addresses to allow.
Per host or path, you may define multiple ACLs. Each ACL may define one or more rules. You have full flexibility.
Understanding Rule and ACL Order
When a host or path defines multiple ACLs. Each ACL appears in a numbered list in the ACL tab of the Host Configuration or Path Rules area. When an ACL defines multiple rules, the rules appear in a numbered list as well.
.png)
The CDN evaluates each request against each ACL and ACL rule in the order in which they appear in the list, until a match occurs. Once a match occurs, the CDN stops the evaluation without continuing to the end of the list. As soon as a request matches a condition that would cause it to be denied, the CDN denies it. As soon as a request matches a condition that causes it to be accepted, the CDN accepts it.
If the CDN has evaluated all the ACLs and ACL rules in the list and the request has still not been allowed or denied, then the default access setting defined for the Host or the Path are applied.
Example with Multiple ACLs
In this example, there are three ACLs and a default of "Deny all". This is what will happen in production when a request for content in this path is received:
The CDN compares the request with ACL 1, which is set to Allow IP addresses from three specific countries.
If the request comes from one of those countries it is accepted and the process is complete.
If the request does not come from any of the three countries, the CDN evaluates the next ACL in the list.
The second ACL defines a named list.
If the request matches an address on the list, it is accepted.
If not, the system evaluates the next ACL in the list.
The third ACL defines an IPv4 block.
If the request is in the block allowed by ACL 3, the request is accepted.
If not, the system applies the "Deny all" default access setting and denies the request.
Add an ACL
You can add an ACL to a host or a path.
To add an ACL:
Change the Default Access Setting
As soon as you add an ACL to a host or path, the Default Access: Deny All setting is automatically added to the host or path configuration. You can change the value to Allow All, however, you cannot do that until after you've defined at least one ACL rule. After you define an ACL rule, you can edit the default access setting to the value that makes sense for your use case.
To change the default access setting:
Select the Default Access edit icon.

In the Edit Default Access dialog, select Allow or Deny.
Remember, if the ACL rules specify IP addresses that should be denied, then the Default Access setting should probably be Allow. If the ACL rules specify IP addresses that should be allowed, then the Default Access setting should probably be deny.Select Save.
Change the ACL Order
The CDN evaluates the ACLs in the order they are listed. For the ACLs to work the way you want them to, you must list them in the correct order.
To change the order of the ACLs, select the ACL number and drag the ACL to the position where you want it.
.png)
If an ACL defines multiple rules, you can change the rule order in the same way.
Edit an ACL
You can edit a host or path ACL.
To edit an ACL:
Delete an ACL
You can delete a host or path ACL.
To delete an ACL:


