301 jump (. net Edition)

Jump of Status Code 200: 1. metahttp-equivrefreshcontent3. URLdefault. aspx2.Server. transfer (default. aspx); 3. URLRewrite-strictly speaking, this is not a jump, but a jump in URL spoofing status 302: Response. redirect (default. aspx); Status 301 and

Jump of Status Code 200: 1. meta http-equiv = "refresh" content = "3; URL = default. aspx "/2. server. transfer ("default. aspx "); 3. URLRewrite-strictly speaking, this is not a jump, but a jump in URL spoofing status 302: Response. redirect ("default. aspx "); Status 301 and

Jump of Status Code 200:
1.
2. Server. Transfer ("default. aspx ");
3. URLRewrite-strictly speaking, this is not a jump, but a URL "spoofing"

Jump in status 302:
Response. Redirect ("default. aspx ");
Status 301 and redirect: Response. Status = "301 Moved Permanently ";
Response. AddHeader ("Location", "http://www.cnblogs.com/dingxue ");

At that time, the search engine was still silly. Many people used meta refresh to obtain powerful SEO results. Later, it was directly killed by the search engine. After that, many people started to use 302 as the stepping stone and were also killed. For example, they cheated the search engine and had serious consequences. So few people do SEO on the jump, but some inevitable jumps still need to exist. How can we prevent these jumps from negatively affecting them? So someone studied 301 redirection.
I forgot to blind some beginners. The three status codes are described as follows:
200 normal status, nothing happens, normal page browsing is generally 200
301 permanent transfer (Permanently Moved), SEO is required, will transfer the PR and other information of the old page to the new page
302 temporary transfer (Temporarily Moved), a common trick, is also the SEO most likely to be sentenced to fraud

Set in IIS 301
Internet Information Service Manager-> virtual directory-> redirect to URL, enter the target URL to be redirected, and select "permanent resource redirection ".