This article will help you understand how EasyRedir's URL redirection engine processes your incoming traffic and picks which target URL to send your visitors to.

Set Up Tips

1. Hostnames in URLs are not case sensitive, but paths are case sensitive.

So example.com is the same as Example.com, but example.com/path is not the same as example.com/Path.

2. You do not need to specify an HTTP and HTTPS version of the same URL.

EasyRedir handles both protocols automatically (on plans supporting HTTPS) without needing to add them to EasyRedir individually. This means if you add example.com to your source URLs it will forward both http://example.com and https://example.com to the target destination.

3. The order in which you configure redirects in the EasyRedir dashboard does not matter.

The method that the EasyRedir engine uses to determine which redirect to serve is based on exact matching, so it does not matter what order you add redirects to EasyRedir, nor how redirects are displayed to you in the EasyRedir dashboard.

How Traffic Is Served

1. EasyRedir determines which redirect to serve based on specificity of the paths.

The EasyRedir engine always tries to serve an exact match first (to find a redirect that exactly matches the requested URL). If we don't find an exact match, we will fallback to using a redirect on the root path on the hostname of the URL being requested (i.e. the fallback redirect). Again, the order in which these are added to the EasyRedir dashboard does not matter.

Some Examples

Let's look at an example to further understand these concepts.

1. When path forwarding is disabled

Assuming you had the following redirects set up in EasyRedir:

The following redirects would be served:

2. When path forwarding is enabled

Assuming you had the following redirects set up in EasyRedir:

The following redirects would be served:


If you have any questions regarding how EasyRedir redirection works, please don't hesitate to reach out to us. We're happy to help.

Did this answer your question?