Hi,
The problem with the Application.cfm being used to prevent other pages
except index.cfm being used is that it relies on the user not trying to
access something like index.htm which usually gives a 404 page not found
error.
I get around this limitation by placing all the fusebox files into the
child directory as if it would be called on it's own but in the
fbx_Settings.cfm I place a cflocation which points to the root fusebox as
the access point for the requested child circuit. e.g:
parent
child
In child's fbx_Settings.cfm in the <cfif fusebox.IsHomeCircuit> section I put:
<cflocation url="../index.cfm?fuseaction=child.index&#request.urltoken#"
addtoken="No">
Then you are forced back in via the root fusebox but the user still gets to
where they wanted to go. The other advantage of this is that you can tell
people to visit www.yourwebsite.com/shop/ instead of
www.yourwebsite.com/index.cfm?fuseaction=shop.index...
There are probably far more elegant solutions to this problem but this is
one that works for me.
HTH
Dave Phipps
At 18:26 31/05/2002 +0800, you wrote:
>Hi,
>
>To answer your second question, the use of Application.cfm in the
>traditional way, for setting global variables, is discouraged because it
>gets executed *before* the core file, and also because it is ColdFusion
>specific, making it harder to port apps to other platforms. But I can't
>see any reason not to use Application.cfm to prevent direct access to
>fuses - in fact I can't think of any other way to do it in CF (someone
>else will probably prove me wrong here).
>
>HTH,
>Kay.
>______________________________________
>Kay Smoljak Web Developer
>Custom Tags: developer.perthweb.com.au
>
> > -----Original Message-----
> > From: Ney Andr� de Mello Zunino [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, 31 May 2002 6:19 PM
> > To: Fusebox mailing list
> > Subject: Default Fuseaction
> >
> >
> > Hello.
> >
> > The FBX_Switch.cfm in the core files includes the following:
> >
> > <cfcase value="fusebox.defaultfuseaction">
> > <!--- This will be the value returned if someone types in
> > "circuitname.", omitting the actual fuseaction
> > request ---> </cfcase>
> >
> > And the FBX_Fusebox30_CFxx.cfm core file has:
> >
> > if (ListLen(FB_.rawFA, '.') is 1 and Right(FB_.rawFA,1) is '.')
> > //circuit only specified, no fuseaction such as
> > "fuseaction=circuit."
> > fusebox.fuseaction = "fusebox.defaultfuseaction";
> >
> > That covers for the case when a URL is entered with a circuit
> > name *and
> > a dot*, but without the fuseaction. What is the reason for
> > excluding a
> > case such as when no dot is entered?
> >
> > Another (related?) question: what is the "standard" way of handling
> > direct access attempts to circuits or fuses other than the
> > fusebox? The
> > Fusebox 3.0 Tutorial� on Hal Helms' website suggests that the
> > application.cfm file could be used for that purpose. However, I have
> > read on another Fusebox resource that the use of that file is
> > discouraged in Fusebox 3.0. What gives?
> >
> > Regards and may everyone enjoy the world cup,
> >
> > --
> > Ney Andr� de Mello Zunino
> > Media and Technology Laboratory
> > Campus Computing Centre
> > United Nations University
> >
> > [1] http://www.halhelms.com/index.cfm?fuseaction=tutorials.detail
> >
> > >
>
============================================
Phipps CF Development
Oxford, Oxfordshire.
Telephone: +44(0)7718 896696
http://www.phipps-cf.co.uk
============================================
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
