Review available match types for Request Control
Before you start setting up your Request Control rules, review the match types available with this Cloudlet:
Match Type | Matches Based on | Wildcard Support | Case Sensitivity Support | Multiple Value Support |
---|---|---|---|---|
Cookie | a combination of cookie name and cookie value. | ✓ | ✓ | ✓ |
Default | any and all incoming requests. | |||
Device Characteristics | a list of available device characteristics. | |||
File Extension | the file extensions to match on. | ✓ | ✓ | ✓ |
Hostname | the hostnames to match on. | ✓ | ||
IP address/CIDR list | an IP address or CIDR list. You can also select whether to use the client IP address from the connecting IP address, the X-Forwarded-For HTTP header value, or either option. | ✓ | ||
Protocol | the protocol to match on. HTTP or HTTPS protocol are the current options, and you can only select one protocol per match. | |||
Proxy | whether the edge platform has determined that the incoming IP address is acting as a proxy. | |||
Query String | the query string values to match on. For example, name or name=value1 or name=value1 value2 . | ✓ | ✓ | ✓ |
Request Header | a request header value. | ✓ | ✓ | |
Request Method | the method used for the request, like GET or POST . | |||
URL Path | the URL paths to match on. For example: /clothing/children/shoes/shoe1.jpg | ✓ | ✓ | ✓ |
User Location Data | a combination of the following geographic categories: continent, country, and region/state. | ✓ |
Updated almost 2 years ago