Matt: What context is the 404 handler running in? It may be that CF is treating the handler as if it were located in the same directory as the file that was requested instead of where it actually resides. In other words, instead of building the relative path from where the 404 handler is physically located, build the relative path from where the requested resource would have been located. This is really something of a long shot but since the 404 handler is a special case for CF templates and "true" relative paths haven't worked for you, it may be worth a shot.
BTW, you shouldn't have to use a mapping/absolute path as others have suggested. CFINCLUDE handles relative paths very nicely, thank you. -- Mosh Teitelbaum evoch, LLC Tel: (301) 942-5378 Fax: (301) 933-3651 Email: [EMAIL PROTECTED] WWW: http://www.evoch.com/ > -----Original Message----- > From: Matt Robertson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 21, 2005 8:02 PM > To: CF-Talk > Subject: Re: Whats wrong with this friendly URL idea? > > > On 12/21/05, Ian Skinner <[EMAIL PROTECTED]> wrote: > > I just created a test and it worked for me. Just to be clear, > here are the steps I followed. > > There is something special going on with the site-wide and 404 error > handlers that prevent this from working. I tried a different and more > extreme example on a different, CF 6.1 pro server: > > 1. created http://mysecretbase.com/helloworld.cfm, which lets say > resides at c:/websites/mysecretbase. > > 2. Created c:/storage/old/yoohoo.cfm, which contains only the text > "hello world!". This folder has nothing to do with any web root. > > 3. helloworld.cfm contains only the line <cfinclude > template="../../storage/old/yoo.cfm"> > > You can see the result by visiting the url. It works, just as it > should, but the identical technique fails when inserted into a CF site > wide/404 handler. So does the workaround of using a mapping (which > shouldn't be necessary in the first place cuz cfinclude is server side > and is not restricted to pulling files that are under a web root). > > Something other than the code we are writing is getting in the way > here. It is either built into CF itself for this circumstance, or it > has something to do with the fact that I am homing my web root > somewhere else for added security. I know that cfmodule works on a > tag that resides in the same folder cuz I already do it. Haven't > tried putting the tag somewhere else to see what happens. > > -- > --mattRobertson-- > Janitor, MSB Web Systems > mysecretbase.com > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:227520 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
