but if you do pass the .cfm in the url (assuming that all your pages are
cfm) , and set in the application file to redirect if its not the index.cfm,
then people shouldn't be able to get to any other files, right?
----- Original Message -----
From: "Todd Ashworth" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Friday, January 12, 2001 9:15 AM
Subject: Re: passing page name through url
> That's how I build all of my sites actually. One thing you might want to
do
> is separate the extension from the file name. This will help prevent
people
> from running files that they shouldn't. Also .. watch your directory
> structure very carefully. If you put something in the wrong place,
someone
> could get to it easily.
>
> | <cfswitch expression="#request.page#">
> | <cfcase value="dspMain,actMain">
> | <cfinclude template="#request.page#.cfm">
> | </cfcase>
> | </cfswitch>
>
> Todd Ashworth
> www.janty.com - We put the `u` in music!
>
> ----- Original Message -----
> From: "Brandon Paolin" <[EMAIL PROTECTED]>
> To: "Fusebox" <[EMAIL PROTECTED]>
> Sent: Friday, January 12, 2001 8:59 AM
> 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
