Skip to main content
All CollectionsManaging URL redirects
Understanding redirect matching settings
Understanding redirect matching settings

Learn about the options available on source hostnames that affect whether a request matches one of your redirect configurations.

Updated over a month ago

Each source host in your dashboard has settings that you can configure that affect how we match an incoming request to our URL redirection engine against the URL redirection configurations you've set up in your dashboard.

Ignore Case When Matching Paths and Query Parameters

If you enable the Ignore Case When Matching Paths and Query Parameters setting our URL redirect engine will treat both uppercase and lowercase letters in the path and query parameters as equal. For example, with this setting enabled, the following requests would all be interpreted as the same request:

The default setting is to treat uppercase and lowercase letters as different. If you change this setting it may take several minutes for it to become active.

Ignore Ending Forward Slashes on Paths

If you enable the Ignore Ending Forward Slashes on Paths setting the URL redirect engine will ignore any slashes present at the end of the requested path. If this setting is enabled the following requests would all be interpreted as the same request:

The default setting is to treat all slashes found at the end of request paths as different.

Insider tip: You can apply your source hostname settings on an organizational level through the default hostnames settings. Learn more about it here.

Let us know if you have any questions about how we handle matching an incoming request to your URL redirect configurations. We're happy to help!

Did this answer your question?