Russ, By default IIS is set to either send Detailed if local or Custom if remote, if one is changing this setting on a remote server it is likely to be a production server and should not be be touched. At least this is the way I read that, but again you don't need to touch any IIS setting when dealing with ColdFusion errors at all.
Which can be explained in more detail here. http://www.iis.net/learn/troubleshoot/diagnosing-http-errors/how-to-use-http-detailed-errors-in-iis Regards, Andrew Scott WebSite: http://www.andyscott.id.au/ Google+: http://plus.google.com/113032480415921517411 On Tue, Apr 7, 2015 at 3:28 AM, Russ Michaels <r...@michaels.me.uk> wrote: > > by default IIS will display a 500 server error if it gets back a CF error > page as it doesn't know what to do with it as it doesn't send a valid error > code that matches any IIS errors. > In order to see the REAL cf error you have to turn on detailed error > messages in IIS, or you have to create a custom error page to display > instead of the 500 server error. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:360402 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
