debugging marches on... I took IIS 404 behavior back to default to simplify debugging. So ignoring the weirdness I described earlier re: the IIS 404 handler, if I just concentrate on the CF handler, I am saddled with a template that is not firing.
I put up a thread on Stack Overflow. One suggestion was to set error page properties to 'detailed error pages' and this did in fact let the CF template run... but it also displays detailed error pages onscreen on all other types of errors. CF9 works fine with IIS set to 'Detailed errors for local requests and custom error pages for remote requests' Another solution offered in the same thread suggested I turn off HTTP status codes in CF Admin. This too solved the problem and the template fired... but when you do that the only code returned by CF is a 200 that you can't redress with a cfheader. Very bad for SEO. A third suggestion was to stick a cfmail statement into the error template to demonstrate the template was in fact firing, but IIS is keeping it from being displayed. Working cfmail code was inserted and ... no mail was sent, which seems to reinforce the impression that the template is not firing at all. -- --m@Robertson-- Janitor, The Robertson Team mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:356813 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
