the problem with serving files using CF is that you are putting
considerable extra load onto CF, as it has to load the load into memory and
then serve it. If its a busy site serving lots of files then this may well
overload your cfserver, especially if your on shared hosting.
by using .htaccess as I said, you do not involve CF in the task at all.
If you want to control permissions on other parts of your app as well, then
this is also easy to achieve, as you can pass the login used from htaccess
to CF and then use that for your role based security within your cf app as
you already do.
On Fri, Aug 10, 2012 at 8:07 PM, <> wrote:
> >> I set the appropriate meta
> tags and robots.txt to tell the search engines to not spyder the site.
> Only well behaving bot will follow the robot.txt recommandations.
> There are also bad bots which don't care reading the file, and very bad
> bots which do read the file in the only purpose to request what you want to