was just a general reply to the last message in the thread, as I'm sure most folks do.
On Wed, Mar 28, 2012 at 4:58 PM, Andrew Scott <andr...@andyscott.id.au>wrote: > > Russ, that is very true. But if you have the Status Code switched on > ColdFusion will send a status 500, 404 etc. Which IIS will then see, and > you will still not see any ColdFusion error. Now as I have seen the blank > screen on ColdFusion throwing these status codes with IIS, that solution > worked for me. > > Your solution, is only for turning on more detailed ColdFusion errors. > Which is no good if the HTTP status codes are being sent from ColdFusion in > the first place, because IIS will take over with its error pages. > > Needed to clarify that as you replied to me. > > > -- > Regards, > Andrew Scott > WebSite: http://www.andyscott.id.au/ > Google+: http://plus.google.com/108193156965451149543 > > > > > > On Thu, Mar 29, 2012 at 2:53 AM, Russ Michaels <r...@michaels.me.uk> > wrote: > > > > > on IIS7 by default a CF error will result in a 500 server error. > > You need to enable detailed errors on the site in question. > > > > select the site in IIS > > click the ERRORS icon > > click feature settings on the right > > now enable detailed errors and save. > > > > now see if you get a cf 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:350570 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
