for CF sites it should be fine to simply enable errors in IIS as all your errors are going to be returned by CF anyway. The only exception would be if your running a mixed site with CF and other technology. In which case as long as you separate your technologies into different folders, you can put a web.config into each folder with different settings. So CF could have errors enable and asp.net disabled for example. Or you could simply create a custom error on IIS and have that displayed instead.
have you tried using the sitewide error template in CF, I don't think that causes the server 500 error. On Mon, Jul 2, 2012 at 6:56 PM, Justin Scott <leviat...@darktech.org> wrote: > > > ... So this brings up the question now of what's the full > > purpose of the CFAdmin setting and it's use with the IIS > > setting for Details vs Custom IIS error pages? > > Basically IIS is looking at the response codes from an application and > when it sees anything other than normal 200 (OK) code (and some > others, such as 30X redirects), it will look at the error handling > settings to see how it should respond to the user. If the custom > errors are enabled for the visitor in question, then it will use > whatever is set in the IIS settings (e.g. display a static HTML file, > a generic error code, redirect to a page, etc.). This is to prevent > any sensitive information from leaking out of the server in the case > of an error (such as the info that would normally come from a robust > error handling exception in ColdFusion). IIS is helping to protect > the security of the application and handle error conditions for you. > > The setting in the CF admin controls what status code is sent out when > there is an error. Normally when CF encounters an error it will send > a 500 (Internal Server Error) code which IIS then intercepts and > handles as described above. If you change this setting, you can have > CF send a 200 (OK) code even in the event of an error which bypasses > the IIS error handling routines and allows whatever output CF > generates (page, error page, custom error handler output, etc.) to get > through just like any other regular content. IIS just sees it as a > normal response at that point and allows it through. > > > -Justin > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:351796 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
