# Manage advanced redirects

> Advanced redirection configuration options available in the Uniform digital experience composition platform.

Source: https://docs.uniform.app/docs/guides/composition/url-management/redirects/advanced-redirects

The **Advanced** tab offers more granular control over the redirect being authored. Each main data point selection uncovers with additional configuration options to ensure the desired outcome.

## Advanced redirect options

### Source

| Configuration | Control | Default | Options |
| --- | --- | --- | --- |
| Project map node | Select a node | False | **Must match domain**: Protocol and domain are taken into account for incoming requests. Any requests that don't match the domain defined in the source will never be matched. This is useful when setting up specific redirects for a pre-production environment that are only executed on a particular domain but not production. |
| URL | Text field |  | Enter the absolute or relative path for the source URL. |
| Common configuration option | Check box | True | **Retain query string from incoming request**: Retains the incoming request's query string parameters to be applied to the target. It's useful to pass along things like Google Tag Manager campaign parameters to a new location. Set this to false if you wish to disregard any query string parameters on the user's request with the intent to rewrite them with new parameters from the target. |

### Target

| Configuration | Control | Default | Options |
| --- | --- | --- | --- |
| Redirect type | Dropdown list | 301 | - **301**: permanent redirect<br>- **302**: temporary redirect<br>- **307**: temporary redirect that preserves the HTTP method<br>- **308**: permanent redirect that preserves the HTTP method<br>- **404**: not found<br>- **410**: gone |
| Project map node | Select a node | True | **Preserve incoming protocol**: The target will use the same protocol `http://` as the incoming request. This option is only available if the target defines a protocol.  <br>**NOTE**: This won't be displayed if the redirect type is 404 or 410. |
|  |  | True | **Preserve incoming domain**: The target will use the same domain (for example, `uniform.app`) as the incoming request. This option is only available if the target defines a domain. |
| URL | Text field |  | Enter the absolute or relative path for the URL the redirect will resolve to.  <br>**NOTE**: This won't be displayed if the redirect type is 404 or 410. |
| Common configuration option | Check box | False | **Stop executing rules after this one**: If the result of this redirect targets a URL that's the source for another redirect, resolve that redirect as well. |

## Create an advanced redirect

1. In Uniform, navigate to **Experience > Redirects**.
2. Click **Add redirect**.
3. Toggle to **Advanced** tab.
4. Choose source type, either **project map node** or **URL**.

   1. If you selected project map node, select a node from the structure provided.
   2. If you selected URL, enter a free-form URL. It can be a relative path or an absolute URL.
5. Make the appropriate selections in the **more options** section for the source.
6. Select the appropriate redirect type from the dropdown list.
7. Choose target type, either **Project Map Node** or **URL**

   1. If you selected project map node, select a node from the structure provided.
   2. If you selected URL, enter a free-form URL. It can be a relative path or an absolute URL.
8. Make the appropriate selections in the **more options** section for the target.
9. Click **Save**.
10. The redirect listing is displayed.

## Delete a redirect

1. In Uniform, navigate to **Experience > Redirects**.
2. Find the redirect definition you wish to delete.
3. Click the  button and click **Delete**.
4. Click **OK** to delete the redirect.

## Edit a redirect

1. In Uniform, navigate to **Experience > Redirects**.
2. Find the redirect definition you wish to delete.
3. Click the source of the redirect definition.
4. Edit the fields you want to change.
5. Click **Save**.