Hello all,
I have a Form that is creating separate CSV's for each submission. I want to place these CSV's in a directory (easily done).
The hard part is finding an app that will allow access to download and delete the file off of the server. I know the FileManager is available. The problem is I can still access the CSV without having to be logged in to the admin panel, assuming I know the path and the filename.
Is there an app (doesn't necessarily have to be CMSMS compatible) that will allow me to download/delete files in a directory, but will prevent a download if they put the direct path in for the file (ex. www.mysite.com/directory/myFile.csv)?
File management that prevents unauthorized downloads/access
File management that prevents unauthorized downloads/access
If all else fails, use a bigger hammer.
M@rtijn wrote: This is a community. This means that we work together and have the same goal (a beautiful CMS), not that we try to put people down and make their (voluntary) job as difficult as can be.
-
calguy1000
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: File management that prevents unauthorized downloads/access
well, direct urls like that bypass the app. You'd have to protect that directory with a .htaccess file
but the .htaccess file still has to allow the local host to access the directory.
but the .htaccess file still has to allow the local host to access the directory.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Re: File management that prevents unauthorized downloads/access
I tried the .htaccess and found that it wouldn't allow the app to have access. I never thought of giving access to the localhost.
What type of allow should I give it. Should I use the actual IP of the machine or 127.0.0.1?
What type of allow should I give it. Should I use the actual IP of the machine or 127.0.0.1?
If all else fails, use a bigger hammer.
M@rtijn wrote: This is a community. This means that we work together and have the same goal (a beautiful CMS), not that we try to put people down and make their (voluntary) job as difficult as can be.
