Hello and thanks for your time. I am using fusebox to create a coldfusion application. I have been asked to move certain files outside (above) the web root so they are not accessible via the web browser. I can no longer directly link to them, which is the point.

Is there a coldfusion script that can do this? I still want to get to them, but considering where they are now residing I do not know how to do that. If anyone can point me in the right direction, that would be wonderful! Not looking for any code at this point, just some direction. Thank you!

Look into using cfcontent. It is often used to serve up documents from a protected area.

Sansclue,
Thanks for the info. I have researched and implemented cfcontent. I have placed all sensitive documents above the web root and then created an actionpage to target them in their new location.

I'm using fusebox to create this app. Not sure if you are familiar with it. Actions are basically targeted using the url



getFile then has a fuseaction that points to a coldfusion action page (a fuse) that does the work. It's an interesting way to create an app.

I'm trying to pass variables in the query string, but it does not seem to like it. Here's what I am doing...



On the other end, the actionpage when processed give me an error that filePath is undefined. I ran a cfdump on the page that has the above link and the filePath returns a positive path to the file.

Am I appending the url properly to pass the variable? I've tried several combinations but I cannot seem to get it right. Thanks for any help you may be able to provide.

Cheers!

OK, on the action page when I reference the passed variable I am successfully using #URL.data# instead of just #data# and it seems to work fine. In other situations I have used the latter and it has worked fine. Perhaps this has something to do with the fact that I am using Fusebox to build this app.

Cheers!!

No, it just has the wrong parameter name. The syntax is:

paramterName=parameterValue

So if want it to be called "filePath", use that name instead of "data".

... &filePath=#filePath#"...>



This post has been edited by sansclue: 20 Apr, 2009 - 02:50 PM

sorry, cant help...

Sansclue, thanks again. I was giving you the wrong information. This is how I have the URL...


So I tried referencing #data# in the action page. This does not work unless I use #URL.data#

Then use #url.data# ;-) It is the correct and it is better to scope your variables like that anyway. ie Use #scopename.variablename# instead of just #variablename#.

Thanks Sansclue. Here's what I ended up doing...

Here's a URL example


Then fusebox would map to the appropriate action page which is the following...


This works great!

Cheers!

This post has been edited by midasxl: 27 Apr, 2009 - 08:05 AM