The CF administrator will only let you set up 1 page to handle CFM 404s for the entire server, which introduces an issue if you are hosting multiple sites and wanted to use a 404 handler for each. To get around that, I have done something like this in the past:
Missing Template Handler: /mappedPath/404controller.cfc 404controller.cfc ---------------------------------------- <cfif CGI.server_name CONTAINS houseoffusion.com> <cflocation url="http://www.houseoffusion.com/404.cfm"; addtoken="no" /> <cfelseif CGI.server_name CONTAINS mysite.com> <cflocation url="http://www.mysite.com/404.cfm"; addtoken="no" /> <cfelse> <cflocation url="/mappedPath/404default.cfc" /> </cfif> .... with 404default.cfc being something very generic. Of course you can pretty this up with a switch statement, DB call, or whatever else you would like (I tried to keep the example simple). Jake Pilgrim >On 6/6/07, C. Hatton Humphrey <[EMAIL PROTECTED]> wrote: > > > > >Make sure is a it Message Type = "URL" type error handler and not a file >based. >Then it's /error.cfm from the root of the website for the URL > >Also this will not handle missing .cfm pages unless you set that in >coldfusion administrator. "Missing Template Handler" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:280303 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
