> I found a simple way to "crash" CF.. just include a file in itself..
> or an endless loop.
> I think that uses up all available resources until cf can't
> function anymore!
>
> For example: in header.cfm
>
> -----------------------
> ...
> <cfinclude template = "header.cm">
> ...
> ----------------------
I know this probably sounds like I'm putting people down by this, but only a
moron would call the template from within itself without parameters or
conditions
It's rather like having
<cfloop condition="1 is 0">
and never having a <cfbreak>
I've seen some pretty shocking code in my time, but usually, neverending
loops are accidental, not (pseudo)deliberate like including the current
template within itself
Philip Arnold
ASP Multimedia Limited
T: +44 (0)20 8680 1133
"Websites for the real world"
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
