CFContent Issues

[v_roma]

Hi everyone,
Basically, the summary says it all. I can get CFCONTENT to work only if the file is located in a web-accessible folder but not in a non-web acessible one. This kind of defeats the purpose of using CFCONTENT for me. I don't have access to server admin so I was wondering if you need to turn something on so that the non web-accessible folder is accessible by the server itself using CFCONTENT.
Hope that made sense.
Thanks,
v_roma

[Newsgroup_User]

Not 100% sure, but this may be a place where one needs to use a
ColdFusion mapping (AKA not an IIS, Apache, other web server mapping).

This is an administration setting, but it may be available in the
administration API. One would define a mapping 'foobar' that points to
any directory on the server. Then one can use this mapping for various
ColdFusion tags.

I'm just not sure if CFContent is one of these tags?

v_roma wrote:
> Hi everyone,
> Basically, the summary says it all. I can get CFCONTENT to work only if the
> file is located in a web-accessible folder but not in a non-web acessible one.
> This kind of defeats the purpose of using CFCONTENT for me. I don't have
> access to server admin so I was wondering if you need to turn something on so
> that the non web-accessible folder is accessible by the server itself using
> CFCONTENT.
> Hope that made sense.
> Thanks,
> v_roma
>

[v_roma]

Thanks, Ian. Maybe somebody out there will know if CFCONTENT requires something like that.

[Mr_Black]

The whole idea of CFCONTENT is to deliver stuff, which is NOT on Web-site path. Most likely, you have a coding error (misspelled file, directory, CFM syntax, etc), or the account the Cold Fusion service is running under, does not have permission to access the specified file. No Cold Fusion mappings involved here, since CFCONTENT uses absolute physical path(s).

[Wilgeno_wnt]

Also make sure you have the whole and correct absolute path to the file specified in the tag. On windows it will be something like d:\my\non\web\folder on *nix type systems it will be something like /my/non/web/path/.

If your sure you have the correct path then it may be a permissions issue. BTW: how did you place the file in the non-web path?