Here's one thing:

What about protecting the direct calling of files other than index.cfm?

This worked fine for me because I put all of my circuits in a folder called "circuits".

I placed the application.cfm, with the code that checks for index.cfm, in the circuits folder.

Here's an example.

Root/ -application.cfm <-- used for whatever

-Index.cfm (fusebox) -LoginForm.cfm (XFAT) -Cart.cfm (XFAT)

/circuits/ -application.cfm <-- checks for index.cfm

/members/ /blocks/ -dsp_login.cfm /queries/ -qry_login.cfm /cart/ /blocks/ -dsp_ShowCart.cfm /queries/ -qry_ShowCart.cfm

Again, all the XFA Templates (XFATs) do is set the fuseaction and include index.cfm (or #request.self#).

<!--- LoginForm.cfm (XFAT) ---> <cfset attributes.fuseaction="members.loginform"> <cfinclude template="#request.self#"> <!--- End LoginForm.cfm --->

So, you can't make a direct call to a file other than index.cfm and XFATs

<!--- Index.cfm --->

<cfset request.fuseaction=listfirst(attributes.fuseaction,".")>

<cfswitch expression="#request.fuseaction#">

<cfcase value="members,cart"> <cfinclude template="circuits/#request.fuseaction#/index.cfm"> </cfcase>

</cfswitch>

> -----Original Message----- > From: billking@hostworks.com [mailto:billking@hostworks.com] > Sent: Thursday, May 10, 2001 4:13 PM > To: Fusebox > Subject: RE: xFATs Anyone? (was RE: XFB question - XFA in MyGlobals?) > > > That is interesting...I have a site highly reliant on search > engine traffic. > > I would like to see if anyone has any critical or otherwise thought > provoking comments on this. > > Signed, > > Bill King > HostWorks INC > http://www.hostworks.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists