301 redirect for IIS Windows Server?

getting 301 redirects to work with IIS

[babynerd]

Hello,

I have an IIS 6 server running with 1 site feeding content to 3 domains (foo1.com, foo2.org, foo3.gov). I would like to do 1 permanent 301 redirect for 2 of them foo1 and foo2 and I know it takes 4-12 weeks to do the redirects. I also know I will have to make a site for each of them. What I don’t know though is will I have to give each site a different port number (ex 80 81 82) and how this will affect the viewing of said sites. Any help with this question would be great. Also Why does it take 4-12 weeks in IIS and only seconds in apache?

Dave

[babynerd]

I also know there is another thread by this same name but I could not post to it.

[jtbell]

Also Why does it take 4-12 weeks in iis and only seconds in apache?

The redirect should take effect immediately in either IIS or in Apache. That is, if you try to go to one site, you end up at the other site and the other site's address shows up in the browser's address bar.

The 4-12 weeks refers to how long it takes for the effects of the redirect to show up in Google searches, with either IIS or Apache.

[Vimes]

Hi,
Could you advise me on the correct server header response. i've just upgraded to IIS6 from 5.

now setting up redirects On 5 gives me a header code like this:

Server Response: [example.com...]
Status: HTTP/1.1 301 Error
Location: [example.com...]
Server: Microsoft-IIS/5.0
Content-Type: text/html
Content-Length: 150

I've done exactly the same on the version 6 but i get the HTTP/1.1 301 Moved Permanently.

now what i've read in the past this is for an apache server and not windows.

so how do i get the correct HTTP/1.1 301 Error

i'm worried that this is the incorrect response and the search engines will have problems with this.

Any help would be greatly appeciated.

Vimes

[edited by: Xoc at 5:25 am (utc) on Oct. 29, 2004]
[edit reason] changed to use example.com [/edit]

[pageoneresults]

You are getting the correct http status which is 301. The Reason Code of Error is the default code for IIS5 which was incorrect according to the specs. Don't worry, the Reason Code does not affect anything. It is the Status Code that does.

It looks like they've corrected that in IIS6. 301 Moved Permanently is the correct Status Code and Reason Code.

[Vimes]

Thanks pageOne,

I'll sleep better now.

[pageoneresults]

Actually I worded that incorrectly above. It should be Status Code and Reason Phrase. Just wanted to correct the terminology.

[Vimes]

Hi,

Pageone if your around could you answer this one for me.

On the Courtesy redirect IIS6 does if a URL doesn't end in a / it redirects to the trailing slash with a 301 much better than IIS5.
But I’m concerned that www.example.com/jp redirects to www.example.com/jp/ which automatically returns the default page in this case index.htm will the search engines see these as duplicate content
www.example.com/jp/
and
www.example.com/jp/index.htm

and if so is there a way I can amend the courtesy redirect to go to the index.htm I’m struggling to get this to happen.

i would like to avoid setting up redirects from /jp/ to /jp/index.htm as this site is very large...

Vimes

[edited by: Xoc at 5:29 am (utc) on Oct. 29, 2004]
[edit reason] changed to use example.com [/edit]