This might be a bit of an odd one. Using older versions of concrete, I have been able to create a folder on my site, outside of concrete, that I can simply use to store files for direct linking and download (.mp3 files, primarily). This allows me to store files on my server in a simple way outside the concrete file structure, and to give simple links to clients who want to download.

However in the latest versions of concrete, I cannot files stored this way to show up - any attempt to access them throws a 404 error (Not Found The requested URL was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.)

It makes sense that concrete would block attempts to see folder contents, for example, but to block an individual file, stored in a folder outside concrete, where the folder's permissions are set to read/read/read ?

What am I missing?

(I have other URLs on my DreamHost, running older Concrete, where this works just fine, so I'm reasonably sure it's not the permissions on my server...)