Whether you sent "HTTP/1.1 301 Moved Permanently" from Witango, ASP, ASP.NET or configured under IIS directly - they all work basically the same, as far as Browsers or search engines are concerned.
Remember, HTTP is a layer independent from Witango, the Webserver or the client (browser). Recently I've done a lot of this using all of the above for several different Servers (mine and some customers), including using the 404 trick to a special Witango TAF that did the "301" output, and I had equal success with all the methods. Note: under Witango, it's probably pointless to include the <@userreferencecookie> in the redirect - because the key that is potentially issued will not work under a different domain (the one you redirect to). Hope this helps. Cheers.... Scott Cadillac, 403-281-6090 ~ [EMAIL PROTECTED] ------------ XML-Extranet ~ http://xmlx.ca ~ http://forums.xmlx.ca Well-formed Programming in C# .NET, Witango, MSIE and XML ------------ Witango ~ http://witango.org EasyXSLT ~ http://easyxslt.ca IIS Watcher ~ http://iiswatcher.ca ------------ -----Original Message----- From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, 3 Mar 2004 14:55:32 -0500 Subject: RE: Witango-Talk: Redirects (OT) > I believe this would work, but have never tried it in Witango. > Another method would be to use the ASP method. I have used this and > it works also... > > <% > Response.Status = "301 Moved Permanently" > Response.addheader "Location", "http://www.yourdomain.com/newpageurl/" > Response.End > %> > > Need to name your page something.asp though > > Just My 2 Cents > > >Thanks for the response. > > > >Can you do this with a HTTP redirect with httpHeader? Or is IIS the > only way > >to do this? > > > ><@assign request$httpHeader "HTTP/1.1 301 Moved > Permanently<@CRLF>Location: > ><@var method$URL > >encoding=metahtml><@crlf><@setcookies><@userreferencecookie><@crlf><@c > rlf>"> > > > >Thanks > > > >Steve > >-----Original Message----- > >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > >Sent: Wednesday, March 03, 2004 8:13 AM > >To: [EMAIL PROTECTED] > >Subject: Re: Witango-Talk: Redirects (OT) > > > > > >Do not use a 404. This will kill a robot immediately (google at > >least). A 404 is a page not found and will stop the bot in its tracks. > > > >You should use a 301 redirect. To do this in IIS, go to > >properties/Home Directory. Click a "redirection to a URL." Fill in > >the complete URL including "http://" in the Redirect to: field. Check > >the "Exact URL Entered Above" box. Check the "Permanent Redirect for > >this Resource" box. > > > >>Windows 2003 Web Edition, R:Tango 5.0 > >>Still rewriting all to multi domains/one set of apps. > >> > >>Some of my tafs had to move to different folders. I want to make sure > that > >>browsers are redirected to the new location, but that search engines > will > >>discover page no longer exists and delete from search engine DB. > >> > >>I have 2 possible methods: > >>1) I can use a 404.taf to redirect > >>2) I can use IIS 60 redirects for each page > >> > >>Both will get the browser to the correct location, but how do search > >engines > >>spiders react to each method. Do they realize that the page no longer > >exists > >>with either method? > >> > >>Thanks > >> > >>Steve Fogelson > >>Internet Commerce Solutions > >>_____________________________________________________________________ > ___ > >>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > > > >-- > >______________________________________________________________________ > __ > >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > >______________________________________________________________________ > __ > >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > -- > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf