CodeStore.net comments on "Redirecting Users After Moving a Database"

Reply from anil

anil — Wed, 01 Aug 2012 20:23:40 -0500

What is URL REDIRECTION?How can i use this concept in my .net?

my task is i have generated one url like this "http://example.com/"

I am passing one pearameter like "http://example.com/Empno=1"

I want to display Ename in Database table that corresponding "Empno"

plz Help me Give me one simple example

I am new this concepts

plz Help me send source code to my mailID:mandla.anilbabu@gmail.com

Reply from Fredrik Stöckel

Fredrik Stöckel — Fri, 17 Feb 2012 16:07:21 -0600

Very creative solution!

Fredrik

Reply from Jake Howlett

Jake Howlett — Fri, 10 Feb 2012 03:23:25 -0600

Agreed Ferdy. My example was poorly thought through. In my real world scenario the subdomain wasn't machine-name-based, but role-based. A better example might have been to move a database from sales.acme.com to marketing.acme.com.

Reply from Jake Howlett

Jake Howlett — Thu, 09 Feb 2012 15:59:30 -0600

Normally I'd agree, but it's not always the best technical solution that wins. Sometimes there's an over-riding business reason not to. For example, the "corporate message" that needs to be conveyed as the reason for the move.

Reply from Palmi

Palmi — Thu, 09 Feb 2012 13:48:46 -0600

I aggree with Sven , its better then do a "hack" coding.

Reply from Sven Hasselbach

Sven Hasselbach — Thu, 09 Feb 2012 10:54:49 -0600

Another way is to use Web Site Rules in the Global Web Settings and use substitutions and/or redirects to accomplish this.

Reply from Ferdy

Ferdy — Thu, 09 Feb 2012 09:18:21 -0600

Jake,

Great tip, but I'd like to add that preferably one does not hand out production URLs that have a machine/hostname in the URL. By using a "friendly" hostname, moving a site is a matter of changing the DNS, and all your SEO value will remain the same. Ideally you wouldn't even include a file path in the URL, but that's harder to accomplish.

Reply from Dragon Cotterill

Dragon Cotterill — Thu, 09 Feb 2012 09:15:23 -0600

Been there. Done that. Doesn't stop them remembering where old pages were, and doesn't stop all bots.

Reply from Jake Howlett

Jake Howlett — Thu, 09 Feb 2012 07:52:19 -0600

More specifically you would probably want to just prevent crawling of the DB which has moved. The content of the robots.txt would then be like:

User-Agent: *

Disallow: /database.nsf/

# Allow ALL others

User-agent: *

Disallow:

Reply from Sven Hasselbach

Sven Hasselbach — Thu, 09 Feb 2012 06:30:16 -0600

You can stop the spiders from crawling your pages by adding a robots.txt-file in the \domino\html\ folder.

Reply from Dragon Cotterill

Dragon Cotterill — Thu, 09 Feb 2012 05:55:32 -0600

"As I understand it, after a while it will stop indexing that content and forget it ever existed."

No they don't. I am still getting hit for content which was removed/moved 8 years ago. Baidu, Googlebot and a slew of others still visit regularly and generate a shed load of error reports in my stats. I have tried 301, 302, 404, even 401 to get them to sod off. In the end I tried putting blank content on some pages with noindex/nofollow and it still does no good.

It seems that once the content is there bots assume it'll always be there ad infinitum.