On Dec 5, 9:55 am, "Evan" <[EMAIL PROTECTED]> wrote:
> fyi, only the following physical directories are accessible in cakephp:

Hi Evan,

That's a bit misleading.

If you create on your server /CustomDir/something.txt, you can access
it with the url /CustomDir/something.txt; if you try to just access the
folder, that will be handled by cake because the url doesn't map to a
file.

Moreover, that's the same for any and all folders under where cake is
installed (if you have mod_rewrite enabled), there is nothing magic
that prevents cake form capturing incorrect files/img/css/js urls; If
the url does not relate to a phycical file (either directly, or after
being rewritten to the webroot if appropriate), cake will be put into
action, compare:
http://www.cakephp.org/img/donate/cake100donate.png
with
http://www.cakephp.org/img/NotHere.anything

BTW if you put files in the webroot/files folder, that means that if
you know the url you can download the file, which may not be what is
desired (I don't know). If you want to control access to files, it's
much better to follow an approach similar to how Mariano has suggested
(but with the files inaccessible directly via a url if you want to
protect them), and serve the files to the user.

HTH,

AD7six
Please note:
The manual/bakery is a good place to start any quest for info.
The cake search (at the time of writing) erroneously reports less/no
results for the google group.
The wiki may contain incorrect info - read at your own risk (it's
mainly user submitted) :) You may get your answer quicker by asking on
the IRC Channel (you can access it with just a browser
here:http://irc.cakephp.org).


--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"Cake PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to