I would expect the status code returned would be whatever status code is provided by the CF page performing the lookup. The webserver doesn't care what status code is returned -- it may default to 404, but I would expect if you chose a CF page for your 404 page and then used <cflocation> or <cfheader> a status code provided by either of these tags would replace the default 404 status code.
> Jeff, > While that works, doesn't it mean that HTTP status code > returned is still > 404? > Could be enough to make the googlebot not even index the > page content. > Just a thought > ~k s. isaac dealey 954.522.6080 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://macromedia.breezecentral.com/p49777853/ http://www.sys-con.com/author/?id=4806 http://www.fusiontap.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:204263 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
