IP address/CIDR list
Allows you to match based on IPv4 and IPv6 addresses and CIDR lists.
For IPv6 CIDR lists, use the shorthand notation. For example, if the full notation is 2001:0db8:0001:0002:0000:0000:0000:0001/32, enter this instead: 2001:db8:1:2::1/32.
All Cloudlets support this match type.
For this match type, enter the IP addresses and CIDR lists in the text box provided.
If you have a large number of values, you can paste them in if you separate them with a space, comma, or carriage return.
Invalid IP Addresses/CIDR Lists
For IPv6, publicly accessible addresses in shorthand notation are valid. See RFC 2732 or RFC 2373 for the specific technical details.
For IPv4, these IP addresses and CIDR blocks are not valid:
|Network Address Type||Invalid Addresses|
|Multicast||188.8.131.52/8 through 184.108.40.206/8|
Client IP Setting
For this match type, you can also select whether to use the client IP address from the connecting IP address, the X-Forwarded-For header value, or either option.
When a client connects to the edge platform using an HTTP proxy or a load balancer, the X-Forwarded-For (XFF) HTTP header identifies the originating IP address of that client.
This match type uses the following operators:
|Value||The rule is true when||Example|
|the incoming request includes one of the IP addresses or CIDR lists included in the rule’s if clause.||The rule includes a match where the IP address is 220.127.116.11. In this instance, only requests coming from the 18.104.22.168 address are valid.|
|the incoming request does not include one of the IP addresses or CIDR lists included in the rule’s if clause.||The rule includes a match where the IP address is 22.214.171.124. In this instance, any request is true that doesn’t come from 126.96.36.199.|
Updated over 1 year ago