On 12/22/05, Mosh Teitelbaum <[EMAIL PROTECTED]> wrote:
> Perhaps you have some other code problem in the 404 handler?
Nope. My 404 handler is also my site wide error handler (you can just
specify both as the same template in the CF Admin). It starts like
this:
<cfif not isdefined ("error.diagnostics")>
<cfset variables.GoPage="http://"; & CGI.SERVER_NAME>
<cflocation url="#variables.GoPage#" addtoken="No">
</cfif>
Given the subject of this thread, I have expanded that code, whose
purpose above is simply to kill linkrot. Code from that point onward
is site wide error handler-related.
If you do ANYTHING wrong in a site wide error handler, CF defaults to
raw CF error messaging... with no clue as to what the error was in the
handler. If the code wasn't sound CF would happily explode with a raw
error that flags the original error, not the one thrown by the handler
(which you have to debug on your own... been there, done that).
--
--mattRobertson--
Janitor, MSB Web Systems
mysecretbase.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:227557
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
