Ian Skinner wrote: > Instead of a page with content to try and head off the robots, you could > try sending the 410 "Gone" HTTP Status Code: > > > 410 Gone > > Good idea - for when I get the rest of my issues figured out (i.e. how to centralize all the folder related stuff). :D
I'm realizing now that it's not an IIS issue, but a CF issue, that I need to deal with. All these mini-sites that exist or have been deleted, are (naturally) all built around a central 'index.cfm' page, passing IDs in the URL to determine what page in the site to serve up. Since it's a ..cfm page that has been indexed by web crawlers, its a .cfm page they're tapping - and the IIS error messages don't come into play, it becomes a CF error "File not found: /folder/file.cfm". So in these cases, if I can just serve up (as you suggested) a page with 410 in it, that would work fine. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion 8 - Build next generation apps today, with easy PDF and Ajax features - download now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288809 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
