Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'd just like to hear about any experience creating a (simple) site for redirecting requests.

Basically we have multiple domains, but as we add more domains and change URLs, there is a huge problem of maintaining old links.

When discussing this we are considering using one constant site to determine where the present url is located.

The idea would be pretty simple, just e.g. and then a parameter to find a database row which would contain e.g. domain, parameters, and any other necessary fields to redirect successfully.

for example: would read the new domain e.g. and the parameters id=324324324&id2=34234 so the controller would just redirect to

Is this a good way to handle changing URLs as the domains and URLs change? Are there downfalls to this approach, or better ways to go about URL change?

share|improve this question
up vote 2 down vote accepted

The best way is to issue HttpResponse.RedirectPermanent with the new location and you can do so from your 404 page code-behind to see if the location they're trying to reach is the old one so you don't need a new site.

share|improve this answer
This sounds like an interesting idea, then a skeleton app can exist which just handles 404 errors and redirects from there (if needed). – lko Jun 20 '13 at 9:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.