If you use <cfinclude ...> in your index.cfm instead of <cflocation...> you
could use HTTP_REFERER.
Ren�
----- Original Message -----
From: "Jim Stahlin" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Thursday, May 03, 2001 2:33 AM
Subject: Re: RE: RE: RE: Managing program flow
> They could enter http://mysite.com/step2.cfm but I can also easily check
to see that they came from http://mysite.com/step1.cfm. With FB I only see
that they came from http://mysite.com/index.cfm.
> I can't seem to find a cgi variable that has the REFERER query string.
> All in all it is really nitpicking but I have seen many sites that allow
you to skip steps in the checkout process and it allows the user to skip
things like sales tax and order totaling.
>
> >>> [EMAIL PROTECTED] 05/02/01 19:19 PM >>>
> What are "standard fuseaction names"? Couldn't someone just as easily
enter
> in http://mysite.com/step2.cfm as
> http://mysite.com/index.cfm?fuseaction=step2
>
> Are you thinking of fuses instead of fuseactions like app_globals.cfm?
>
> I'm confused,
> NAT
>
> > -----Original Message-----
> > From: Jim Stahlin [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, May 02, 2001 4:58 PM
> > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: Re: RE: RE: Managing program flow
> >
> >
> > The program flow is more apparent in Fusebox because of the
> > standard fuseaction names. If I want to skip some step I can try
> > to pass fuseactions to the site that skip some steps.
> >
> > >>> "Nat Papovich" <[EMAIL PROTECTED]> 05/02/01 18:47 PM >>>
> > Hopefully I don't sound like a person who hasn't done too much non-FB CF
> > worik, but why is the program flow more apparent in Fusebox? Is
> > that because
> > you have named your fuseactions step1, step2, step3, etc?
> >
> > Using a session variables are a really great way to do it, you could
also
> > check cgi.query_string to make sure the user came from the previous
> > fuseaction step.
> >
> > NAT
> >
> > > -----Original Message-----
> > > From: Jim Stahlin [mailto:[EMAIL PROTECTED]]
> > > Sent: Wednesday, May 0, 2001 4:13 PM
> > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > > Subject: Re: RE: Managing program flow
> > >
> > >
> > > I agree that you have this problem in non-CF sites. But the
> > > program flow is much more apparent in a Fusebox site than in
> > > other sites. I restricted access using session variables and am
> > > in the process of converting the site to fusebox. Other than
> > > using a step variable does anyone know of another way to do this?
> > >
> > > >>> [EMAIL PROTECTED] 05/02/01 18:06 PM >>>
> > > Couldn't they do that in a non-CF site too?
> > >
> > > What you're talking about sounds to me like a regular
> > programming process
> > > problem. You could set a client variable on each page with the
> > > step number,
> > > and send bad users to the right page.
> > >
> > > NAT
> > >
> > > > -----Original Message-----
> > > > From: Jim Stahlin [mailto:[EMAIL PROTECTED]]
> > > > Sent: Wednesday, May 02, 2001 1:50 PM
> > > > To: Fusebox
> > > > Subject: Managing program flow
> > > >
> > > >
> > > > I have a problem in getting my mind around how you can restrict
> > > > the flow f actions in fusebox. I have a site that in the
> > > > checkout process requires the user to pick shipping method, then
> > > > Credit Card info, then Shipping info, then approve the order. If
> > > > I use Fuseactions to do this the user could pass the last
> > > > fuseaction in the URL variable and skip all the entry screens.
> > > >
> > > > Archives: http://www.mail-archive.com/[email protected]/
> > > > Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=sts
> > >
> > >
> > >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
