authorisation code in the individual circuits fbx_settings.cfm.
Most of my apps have a single line application.cfm in the app root which
checks that the file being called is index.cfm and then in child circuits I
secure each circuit (within fbx_settings.cfm) using a bespoke
user/group/user2group model. There are basic 'secure' tags out there that
can help you, cf_secure from www.halhelms.com is a good start,
Jb.
-----Original Message-----
From: Mickael [mailto:[EMAIL PROTECTED]
Sent: 01 December 2003 16:14
To: CF-Talk
Subject: Re: Application.cfm and Fusebox
Thanks John,
This was initiated by me trying to securing certain circuits and access to
them, I have not been able to successfully secure only one circuit only the
whole app. Can you point me in the right direction on that?
Thanks again
----- Original Message -----
From: John Beynon
To: CF-Talk
Sent: Monday, December 01, 2003 10:48 AM
Subject: RE: Application.cfm and Fusebox
You'll find that most people will use application.cfm to catch direct
access
to files other than index.cfm and redirect them to index.cfm in that
event.
You can still can use cfapplication in the fbx_settings file though...
Jb.
-----Original Message-----
From: Mickael [mailto:[EMAIL PROTECTED]
Sent: 01 December 2003 15:28
To: CF-Talk
Subject: Application.cfm and Fusebox
Hello All,
I have a question that hopefully someone can point me in the right
direction. I have read that the use of application.cfm is not needed any
more with fusebox and that all my information should be in a
fbx_settings.cfm. Firstly I was wondering if this is correct not to use
application.cfm. And does that mean that I can still use the
cf_application
tag?
Mike
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
