Funny.. this is the third time in two days I have seen this problem (not on this list Kay, you haven't missed anything)
To "secure" the CFINCLUDE you could add a: <cfif GetCurrentTemplatePath() IS GetBaseTemplatePath()> <cfabort> </cfif> Now... someone browses to this file they are SOL. As far as tracking the actual file... hmm. Are you using SES? (ya.. ok... I don't really have an answer for your second question) > Hi Lee, > > Knew I could count on you to help me out! But then I guess it's that > time of the day when our Yank friends are slumbering. > > What you're describing is exactly the method we were using before, but > with cfcontent not cfinclude. ==^================================================================ 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 ==^================================================================
