Errr... you should always have an Application.cfm that checks to make sure
the user is calling the index.cfm, if not it should redirect them to the
index.cfm like:::
<!--- Check if index.cfm is called, if not then redirect to index.cfm --->
<cfif not findnocase("index.cfm",cgi.CF_TEMPLATE_PATH)>
<cflocation url="index.cfm?fuseaction=badfile">
</cfif>
You should not just have a blank Application.cfm
-----Original Message-----
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, February 07, 2001 2:25 PM
To: Fusebox
Subject: RE: onRequestEnd.cfm
Does CF treat the application.cfm the same way? I was wondering about this
when using fusebox because you typically don't use an application.cfm in
fusebox development. Should we at least put a blank application.cfm in our
application roots also so our apps don't go searching all the way up the
directory structure looking for one?
Rick
-----Original Message-----
From: Ken Beard [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 07, 2001 11:25 AM
To: Fusebox
Subject: onRequestEnd.cfm
Was told something recently that I hear was a "michael dinowitz trick" that
everyone may not be aware of. You should make a OnRequestEnd.cfm in the
root of your cf applications, even if it is blank (needs to contain atleast
a comment). Otherwise cf takes a performance hit when it recurses all the
way to the root looking for one.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
