Thanks Dave, Rodney. That really helped.
It turned out our issue was the same cfscript in the application's header
and the sitewide error handler's header.
When the second instance of cfscript tried to run, it broke the error
handler, thus presenting the raw error to the user.
best,
Chris
On M
The site wide error handler will not run if there is a local error handler,
such as CFTRY/CFCATCH or CFERROR, unless the CFTRY/CFCATCH block rethrows
the error.
-
Rodney
On Mon, Dec 8, 2014 at 8:52 PM, Dave Watts wrote:
>
> > Hi, when can an application bypass the CF v9 site-wide error handle
> Hi, when can an application bypass the CF v9 site-wide error handler?
>
> We host an app, that uses cftry/catch, but that appears to not handle the
> errors correctly. The errors do not trigger the site-wide error handler, and
> the errors are displayed to the users.
>
> The site-wide error ha
Hi, when can an application bypass the CF v9 site-wide error handler?
We host an app, that uses cftry/catch, but that appears to not handle the
errors correctly. The errors do not trigger the site-wide error handler, and
the errors are displayed to the users.
The site-wide error handler works
4 matches
Mail list logo
