-
Notifications
You must be signed in to change notification settings - Fork 158
Handling Redirects
Redirects should be used when article's file name, slug or path has been changed for some reason.
To handle this scenario use the previous_url
property.
---
title: Overview
page_title: Getting Started Overview | RadSplitter for ASP.NET AJAX Documentation
description: Overview
slug: splitter/getting-started/overview
previous_url: controls/splitter/getting-started/getting-starter-overview
tags: overview
published: True
position: 0
---
Note that comma characters in
previous_url
are considered as incorrect. Therefore, such values are not supported. If you happen upon such a case, you should leave it without a redirect, or if it is very important, build and commit a rule directly in the web.config.
As shown in Example 1, the path set to the previous_url
property should exclude only the host and base url of the URL. Therefore, if the old URL is:
http://host/devtools/aspnet-ajax/controls/splitter/getting-started/getting-starter-overview
the value to be used should be:
controls/splitter/getting-started/getting-starter-overview
Note that multiple redirects are not supported. This means that:
A single article can be redirected to a single article, not too many, i.e., a given
previous_url
value can be present on only one file.Several articles cannot be redirected to a single article. If you need such a rule, build and commit one in the web.config. Most likely, there would be some logic so you may be able to handle an entire folder redirect with a single rule.
- Home
- Getting Started
- Deploying Documentation on IIS
- Git and GitHub Workflow
- Handling Redirects
- Markdown Syntax
- Markdown Nesting
- Using Git and Git Bash
- Troubleshooting
- Use VS Diff tool with Git and SourceTree
- [How to deal with the web.config size limit in order to add URL redirects](./How to deal with the web.config size limit in order to add URL redirects)