On 1/3/06, Russ <[EMAIL PROTECTED]> wrote: > I still don't understand what this code is actually doing... do you later > say something like > > <cfinclude template="#request.FilePath#/#CGI.SCRIPT_NAME#"> >
You would use the physical path to run programs like cfdirectory and cffile, where those commands need to be able to pull files from a location on your server. A full path ensures those files can be pulled no matter where you choose to put them. In my case I'm referring to a CMS system that delivers protected files that are pushed to the client via cfcontent and which are kept outside the physical web root. I abandoned relative for full urls when I was faced with a product that allowed users to create their own pages, and designate them as secure if they so chose to do so. That meant the menu links in had to be secure, and all of the menu links out had to NOT be secure. The only way to do that with 100% reliability without even more gymnastics was to use full urls as well. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228328 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
