file renamed after server upgrade

Thanks for your reply Betty,

As for the two suggestion from the communtiy guys, I haven't used the "404
page" approach so I can not give you much comments on it. For running
"*.html" like asp in IIS, I think it is workable just like you configure
html or other static page to be processed by ASP.NET runtime(here you
configure it to be processed by ASP runtime extension), however, one
drawback here is that all the html static files are processed by ASP
extension and if you have some real "html" files(which are originally
processed by IIS directly), you'll lose some performance.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: =?Utf-8?B?YzY3NjIyOA==?= <betty@newsgroup.nospam>
>References: <2980B9D1-792F-47ED-9F5F-0ECF898DBB16@microsoft.com>
<86D82AE5-7B39-4423-BF7C-90C2B9384EBD@microsoft.com>
<L5#eEIWYIHA.5204@TK2MSFTNGHUB02.phx.gbl>
>Subject: RE: redirect search engine highly ranked page
>Date: Wed, 6 Feb 2008 13:58:04 -0800

>
>Hi Steven,
>
>I looked at three options you mentioned here.
>for the first one, meta tag refresh, some articles mentioned that Search
>Engine doesn't like that because of some spammer use this to redirect a
user
>to an irrelevant advertising site.
>Second option, I am not sure if I understand correctly. it seems that it's
>better solution for site restructure. We don't change site map, not change
>all *.htm files to *.asp, but the majority of them. So it is not the most
>proper solution in our case.
>
>Third opiotn, my problem is I am lack of knowledge about ISAPI. So it is
>kind of for me understand it.
>
>So now I am trying to make a decision from these contributoers'
suggestions
>and comments. Which one is better? 404 custom error page redirect or set
>*.html run just like *.asp in IIS. I don't know at all.
>--
>Betty
>
>
>"Steven Cheng[MSFT]" wrote:
>
>> Hi Betty,
>>
>> If you want to keep those html files and let the html file do the
>> redirection, you can consider using the html meta tag to do the
>> redirection. Here is the example:
>>
>> #Redirect to a Different URL using the Meta Tag "Refresh"
>> http://webmaster.iu.edu/tool_guide_i..._metatag.shtml
>>
>> Also, If you have thousands of html pages that need to redirect to their
>> asp version ones, I think you may consider develop a custom ISAPI filter
>> component and plug in your IIS server which intercept those html page
>> requests and redirect to the ASP pages if necessary.
>>
>> #Redirecting ISAPI Filter
>> http://www.15seconds.com/issue/961220.htm
>>
>> #HOWTO: Redirect the browser to a new URL based on Referer
>>
http://blogs.msdn.com/david.wang/arc...rect-the-brows
>> er-to-a-new-URL-based-on-Referer.aspx
>>
>> Also, if you search "ISAPI filter" and "url rewrite", you will find many
>> existing commerical products that do such functions.
>>
>> Hope this helps.
>>
>> Sincerely,
>>
>> Steven Cheng
>>
>> Microsoft MSDN Online Support Lead
>>
>>
>>
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>>
>> --------------------
>> >From: =?Utf-8?B?YzY3NjIyOA==?= <betty@newsgroup.nospam>
>> >References: <2980B9D1-792F-47ED-9F5F-0ECF898DBB16@microsoft.com>
>> >Subject: RE: redirect search engine highly ranked page
>> >Date: Fri, 25 Jan 2008 14:55:01 -0800
>>
>> >
>> >Hi all,
>> >sorry I have to change the original subject since it doesn't make any
sense
>> >--
>> >Betty
>> >
>> >
>> >"c676228" wrote:
>> >
>> >> Hi all,
>> >> Recently we are upgrading and merge our servers. We will move all
*.html
>> >> hosted on a unix system to our windows server. During the migration,
we
>> also
>> >> upgrade almost all of our code, say almost all html pages have been
>> renamed
>> >> to *.asp in order to handle those pages dynamically. But the issue
here
>> is
>> >> our original *.html pages are ranked very highly by search engine. We
>> are not
>> >> sure what kind of redirect will be benign to search engines. And it
>> seems
>> >> that there is no one-page auto redirects solution like you can do
with
>> unix
>> >> system (.htaccess file). On windows server, you have to redirect
>> >> individually. (man, think about if you have thousands of pages on a
>> site.)
>> >> I searched a bit, the following code seems to do the job:
>> >> put this code on the top of every page I wish to be redirected:
>> >> <%@ Language=VBScript %>
>> >> <%
>> >> Response.Status="301 Moved Permanently"
>> >> Response.AddHeader "Location",
"http://www.example.com/yournewpage.asp"
>> >> %>
>> >>
>> >> am I right? But I cannot do this way in the original *.html file
since
>> it is
>> >> not *.asp code. I have to use javascript to do dynamically redirect
>> anyway.
>> >> but what kind of redirect will be beneficial to Search Engine, the
>> >> instantaneous meta refresh redirect or the old page with all the old
>> content
>> >> removed and having a link towards the new page, which way is better,
>> one
>> >> click or no click to get to the new page.
>> >> --
>> >> Betty
>> >
>>
>>
>