Interface default

Matches a request based on the client ip variable value(s).

Matches a request based on one or more cookie values. Keys are case-sensitive cookie names, values are regular expressions to match or null. When value is null then requests are matched for the cookie not being present.

Matches a request based on the specific device property. See: https://docs.edgecast.com/cdn/index.html#HRE/M/Device-Match_Condtions.htm%3FTocPath%3DContent%2520Delivery%7CRequest%7CCustom%2520Request%2520Handling%2520via%2520Rules%2520Engine%7CMatches%2520and%2520Features%7CMatches%7CDevice%7C_____0

Matches a request based on one or more header values. Keys are case-insensitive header names, values are regular expressions to match or null. When value is null then requests are matched for the header not being present.

Matches a request based on the specific location property. See: https://docs.edgecast.com/cdn/index.html#HRE/M/Location-Match-Conditions.htm%3FTocPath%3DContent%2520Delivery%7CRequest%7CCustom%2520Request%2520Handling%2520via%2520Rules%2520Engine%7CMatches%2520and%2520Features%7CMatches%7CLocation%7C_____0

Matches a request based on the HTTP method. Instead of this, prefer using get, post, put, delete, options, and patch methods.

Matches a request based on the origin path (the path after rewrites).

Example

"/products/:id"

Example

/^/products/(.+)$/

Matches a request based on the path. The same path syntax is used by the simple form of the Router class's match method. The path can be an express-style path expression or regular expression. Both express-style path and regular expression need to match the entire path including the leading slash.

Example

"/products/:id"

Example

/^/products/(.+)$/

Matches a request based on one or more query parameter values. Keys are case-sensitive names, values are regular expressions to match or null. When value is null then requests are matched for the query parameter not being present.

Matches a request based on the referring-domain variable value(s).

Matches properties of the response response.

Matches a request based on its protocol / scheme. Unless explicitly specified then https is the default. To serve a route on both HTTPS and HTTP you can specify /https?/ regex. If an HTTP request is not matched against any route, Edgio will automatically issue a redirect to equivalent HTTPS URL.

Matches a request based on the variable value.