you can also use the custom tags that come with CommerceBlock's LoginBlock.
It gives an easy way to protect contect within a fuse, access to a fuse,
access to a group of fuses, or access to the fusebox.
----- Original Message -----
From: "Toby Tremayne" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Friday, April 06, 2001 12:24 AM
Subject: RE: Preventing Access to files with XFB
> well if you want everyone to be restricted to that single index.cfm file -
> just modify the code generally stored in application.cfm to check the path
> as well as the file name.
>
>
> Toby Tremayne
> Code Poet and Zen Master of the Heavy Sleep
> Show Ads Interactive
> 359 Plummer St
> Port Melbourne
> VIC 3207
> P +61 3 9245 1247
> F +61 3 9646 9814
> ICQ UIN 13107913
>
> -----Original Message-----
> From: Ryan Wood [mailto:[EMAIL PROTECTED]]
> Sent: Friday, 6 April 2001 12:26 PM
> To: Fusebox
> Subject: Preventing Access to files with XFB
>
>
> Has anyone developed a custom tag or code snippet to prevent access to any
> file but the root index.cfm in XFB? I've seen the code in the Fusebox Book
> that check to see if "index.cfm" is in cgi.script_name, and redirects if
it
> is not found. That will not work with XFB because there is only one
> index.cfm that is allowed to be called, but there could be many in the
> sub-circuit that should not be accessed. Any thoughts?
>
> Ryan
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
