I think Ben's blog entry sums it up

"A thread on cfcdev today discussed whether ColdFusion debugging should ever
be activated on a production server. The bottom line is no, never turn on
debugging on a production server (you should never need to debug on a live
server anyway, that's what development and testing servers are for). But
what about enabling debugging and simply not listing any IP addresses so
that debug information is not returned? Not good enough. While turning on
and off the display of debugging does have a slight performance impact, the
bigger impact is the gathering and tracking of debug output. The IP address
list simply turns on or off output of accumulated debug information, but
that information will still be maintained if debugging is enabled on the
server. Bottom line, do not turn on debugging on product servers. Ever."



Well, overall it does. But I think he mis-wrote this sentence:


"But what about enabling debugging and simply not listing any IP addresses so that debug information is not returned?"

If you don't list any IP addresses, debugging gets displayed for everybody. So what do you gain by that? I'm not really sure what he was saying there. Bottom line though, his last two sentences have been my rule for years.

Regards,
Dave.

_________________________________________________________________
Frustrated with dial-up? Lightning-fast Internet access for as low as $29.95/month. http://click.atdmt.com/AVE/go/onm00200360ave/direct/01/


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.


CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).

An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]

Reply via email to