Redirect Generator

Scheme: There are two options for the Scheme https and http.

Subdomain: The Subdomain may be left blank if your site is served from the root domain. Example Subdomain: www.. If you serve separate content on your subdomain e.g. app.example.com, you should enter the full domain including app. in the Domain field. Adding the Subdomain www. to this domain would make the final URL www.app.example.com.

Domain: This is the root domain for your site e.g. example.com or app.example.com.

Settings

Remove: Redirects URLs ending in / to ones without it.

Include: Redirects URLs not ending in / to ones with it.

Ignore: Does not redirect URLs with or without /.

Options

Trailing slash on directories: Sets how to handle the trailing slash on requests to a directory in the physical file system.

Trailing slash on non-filepath URLs: Sets how to handle the trailing slash on requests that do not map to a resource in the physical file system. Example: the URL /about-us/team when there is no directory or file on the server at the location /about-us/team.

Trailing slash on query strings: Sets how to handle the trailing slash on the end of a query string. Example: index.php?ref=example.com/about-us/.

Use HSTS preload compatible two-step redirect: For your site to take full advantage of HSTS and be eligible for the HSTS preload list it must redirect all insecure request to secure before redirecting to a different host. This means that a request to http://example.com must first be redirected to https://example.com before it can be redirected to https://www.example.com. You can learn more here.

This setting creates the two-step redirect needed for the subdomain. This is only important if you enter data in Subdomain.

Redirect www to root domain: This setting redirects all request prepended with www. to what you entered in Domain. It will only be processed if the Subdomain field is blank.

Use permanent 301 or temporary 302 redirects: You can choose whether you want the redirects to use permanent 301 redirects or temporary 302 redirects.

Redirect insecure proxy/load balancer requests to https: If your site serves content from behind a proxy, reverse-proxy, load balancer, or CDN you may need to handle X-Forwarded-Proto and X-Forwarded-SSL to upgrade insecure requests from that source.