I'm digging this old-ass post out of the archives because it seems like it was never answered, and I really, really need to get one.
I need to do exactly what the original poster was asking. I have an old html site that is VERY well ranked, and we need to convert to a newer, easier to maintain CF site. My plan was to just create a site-wide 404 error handler, then use cfheader to do a 301 redirect. However, Jim McAtee wrote in this thread that it doesn't quite work: >That's what I was concerned about. I'd heard this years ago but didn't know >if it was >still true. I'm close to an alternative, but... I found out that >ideally, google and others >would like you to return an HTTP 301 (Moved >Permanently) status code. I believe it's >so they can remove the old page >from their index. Which is what I'd like as well. I was >able to get a custom >404 page pointed at a CF template. Problem now is that no >matter what I do >in the template using CFHEADER, IIS always morphs my 301 HTTP >status code >into a 302 code, with its own page output. If I do a GET using something >like >wfetch, then I can see IIS' output - it has the correct new .cfm page >location, but a >302 status code. Somehow I think the custom error page >approach isn't going to get >me anywhere do to the way IIS operates. Has anyone successfully done a 301 redirect WITHOUT using IIS? I'm hosted in a shared environment at CrystalTech, and they flat out refuse to mess with IIS for redirects, period. HELP! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240901 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
