> I have recently installed a custom default error handlers (via CF
> Admin) on several servers (CF5/NT4, CFMX6.1/Linux) and noticed
> that it seems to be taking precedence over any error templates
> set with CFERROR TYPE="REQUEST" as well as most error handling
> done with CFTRY/CFCATCH.
>
> If I have CFERROR TYPE="EXCEPTION" set up on some sites and it
> still runs, but any errors 'exception' cannot trap get sent
> straight to the server's default handler--again, regardless of
> the other error handling I have in place.
>
> This was not the case when I was using the server's default error
> handler. It used to prioritize handlers as follows:
> 1. CFTRY/CATCH
> 2. CFERROR - EXCEPTION
> 3. CFERROR - REQUEST
> 4. Server default
>
> ...
>
> I am hoping someone can shed some light on the subject. Perhaps I
> am missing something fundamental.
This is the expected behavior on CF 4 and newer versions. When you specify a
site-wide error handler, it takes precedence over CFERROR TYPE="REQUEST".
This is very good, as the site-wide error handler can actually do things,
while the error page with CFERROR TYPE="REQUEST" can't really do anything at
all - you can't use CFML tags or functions within that page. The site-wide
error handler isn't a "default" error handler.
Dave Watts, CTO, Fig Leaf Softwarehttp://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
