How to correctly set up the Edge Rule trigger path

Edge rules come with a powerful wildcard matching system in the trigger path. It will allow you to set up smart URL matching. This article provides a few tips and tricks to help you better understand the system and teach you how to properly set it up.

Query parameters are not supported

Currently, the trigger path will not match any query strings or data after the file name. Only the absolute URL path of the request will be matched. 

Matching by file extension

You can easily match a specific extension by entering *.extension as the trigger path, for example:



Matching subdomains

The wildcard * symbol can be used anywhere in the URL. This allows you to easily match all subdomains for example and alternatively match all non-subdomains, for example:



Pay attention to HTTP/HTTPS schema

The trigger path is compared as a whole, so pay attention to make sure the correct http:// or https:// is used. In addition, you could also replace this with a wildcard *:// to match both.

Be careful with the ending slashes

Due to the design of HTTP protocol, the trigger path will always contain an ending slash, even if accessing the root path of your domain. This means that if your trigger path is set to for example, this will actually never trigger the edge rule. In order to correctly detect the root path of your URL, always make sure to add an ending slash such as

Table of Contents

Was this article helpful?
14 out of 22 found this helpful