RE: Cferror and the site wide handler

2006-05-11 Thread Plunkett, Matthew
Thanks very much for clearing this up Matt and Dave, I was using type=request. -Original Message- From: Dave Watts Sent: Wednesday, May 10, 2006 6:21 PM To: CF-Talk Subject: RE: Cferror and the site wide handler snip If I recall correctly, this is the execution order for error handlers

RE: Cferror and the site wide handler

2006-05-10 Thread Ben Nadel
I am a bit confused as to the difference? When I use CFERror, I am using it as a site-wide handler? Then, I can use CFTRY/CFCATCH on individual pages. Are you talking about 404 handlers?? ... Ben Nadel Web Developer Nylon Technology 350 7th Avenue Floor 10 New York, NY

RE: Cferror and the site wide handler

2006-05-10 Thread Steve Brownlee
] Sent: Wednesday, May 10, 2006 2:35 PM To: CF-Talk Subject: RE: Cferror and the site wide handler I am a bit confused as to the difference? When I use CFERror, I am using it as a site-wide handler? Then, I can use CFTRY/CFCATCH on individual pages. Are you talking about 404 handlers

RE: Cferror and the site wide handler

2006-05-10 Thread Plunkett, Matthew
. -Original Message- From: Steve Brownlee [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 10, 2006 2:42 PM To: CF-Talk Subject: RE: Cferror and the site wide handler No, the site wide error handler is specified in the CF Admin under the Server Settings Settings section. That will catch any

RE: Cferror and the site wide handler

2006-05-10 Thread Ben Nadel
, 2006 2:42 PM To: CF-Talk Subject: RE: Cferror and the site wide handler No, the site wide error handler is specified in the CF Admin under the Server Settings Settings section. That will catch any error produced by your site, and the processing will never make it to a page with CFERROR

RE: Cferror and the site wide handler

2006-05-10 Thread Steve Brownlee
It's only advantage, IMHO, is ease of deployment. It's certainly not useful for detailed error reporting like Matt needs. -Original Message- From: Ben Nadel [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 10, 2006 2:50 PM To: CF-Talk Subject: RE: Cferror and the site wide handler Ahhh

RE: Cferror and the site wide handler

2006-05-10 Thread Steve Brownlee
Message- From: Plunkett, Matthew [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 10, 2006 2:45 PM To: CF-Talk Subject: RE: Cferror and the site wide handler Yes, I know where it is set. Thanks for confirming the order that they are processed. Now we have to find a new way to be secure (by hiding

RE: Cferror and the site wide handler

2006-05-10 Thread Plunkett, Matthew
Thanks, I will look at this details.cfm. -Original Message- From: Steve Brownlee Sent: Wednesday, May 10, 2006 3:01 PM To: CF-Talk Subject: RE: Cferror and the site wide handler Matt, I was responding to Ben there. Didn't intend to oversimplify for you since you obviously knew about

RE: Cferror and the site wide handler

2006-05-10 Thread Plunkett, Matthew
Robertson Sent: Wednesday, May 10, 2006 4:23 PM To: CF-Talk Subject: Re: Cferror and the site wide handler Best way to look at error handling: 1. try/catch blocks are for situations where you have an expected potential error (i.e. a mime type failure on a file upload) and you want to handle this known

RE: Cferror and the site wide handler

2006-05-10 Thread Snake
: 10 May 2006 19:45 To: CF-Talk Subject: RE: Cferror and the site wide handler Yes, I know where it is set. Thanks for confirming the order that they are processed. Now we have to find a new way to be secure (by hiding all the junk that default errors reveal), but let the developers see what

RE: Cferror and the site wide handler

2006-05-10 Thread Dave Watts
Is it possible to use both cferror and the site wide handler in MX 6.1? My tests indicate that it is not possible, which is unfortunate. It seems that the site wide will always take precedence. Is there a way around that? My guess is no, but thought I'd check anyway. I care because

Re: Cferror and the site wide handler

2006-05-10 Thread Matt Robertson
On 5/10/06, Plunkett, Matthew wrote: My problem is that I have both 2 and 3 implemented. It seems that 2 never hits unless I turn off 3. Is that expected, or is there a way around it? That ain't right. Are you sure you are using type=EXCEPTION in the cferror statement? Dave Watts put up an