if they tried to access the page directly, the application will redirect
them to the index.cfm
----- Original Message -----
From: "McCollough, Alan" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Friday, January 12, 2001 11:48 AM
Subject: RE: passing page name through url
> As philosophy, I'd try to avoid exposing any specific template names in
the
> URL other than index.cfm. Once a user sees a specific template name in the
> URL, they can try to call the page directly, which will usually generate a
> host of errors.
>
> My philosophy is to keep 'em as ignorant as possible on the actual
> behind-the-scenes workings of the app.
>
> Alan McCollough
> Web Programmer
> Allaire Certified ColdFusion Developer
> Alaska Native Medical Center
>
> > -----Original Message-----
> > From: Brandon Paolin [SMTP:[EMAIL PROTECTED]]
> > Sent: Friday, January 12, 2001 5:00 AM
> > To: Fusebox
> > Subject: passing page name through url
> >
> > are there any problems with passing page names in the url and doing:
> >
> > <cfswitch expression="#request.page#">
> > <cfcase value="dspMain.cfm,actMain.cfm">
> > <cfinclude template="#request.page#">
> > </cfcase>
> > </cfswitch>
> >
> > and just include the pages you want to show in the cfcase list.
> >
> > or even doing:
> >
> > <cfif fileexists("#path#/#request.page#">
> > <cfinclude template="#request.page#">
> > </cfif>
> >
> > and skip the cfswitch.
> >
> >
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
