Mr G Lewis wrote:

> This may be an NT Server question although I suspect it is to do with how 
> Cold Fusion interacts with NT.
> 
> We have an NT Server set up with 3 partitions
> C:  operating system
> D:  applications
> E:  documents
> 
> When NT Server installed it put the inetpub/wwwroot etc on C:
> We moved wwwroot (but not inetpub) to E: and redirected home directory 
> of the web site to that location.   So far so good.
> 
> When we installed CF, CFUSION (application) went on D: and CFDOCS 
> went on E:/wwwroot/ - via the installation program.


This is OK. It is supposed to go there. But keep in mind that generally 
speaking it is not advisable to install the CF documentation on a 
production server, only on test and development servers.


> Now IIS seems ok with this - anything with a htm extension is found but any 
> cfm file is not.
> 
> You can guess that we are new to this server stuff.  Any suggestions?
> 
> The error message that we see is below:  Interestingly, if we use 127.0.0.1, 
> everything works fine.  This is probably a blindingly obvious clue but 
> being novices we can't see how.
> 
> -----------------------------------------snip--------------------------------
> 
> Oops. Sorry for the error...
> 
>             One of several things could be happening:
> 
>              You're trying to execute a ColdFusion page with a
>              URL other than the localhost or 127.0.0.1, or
> 
>              You haven't installed ColdFusion example applications
>              or documentation. 
> 
>             If you tried to execute a ColdFusion page, you just
>             need to: 
> 
>              Execute example applications and ColdFusion utilities
>              locally, using the localhost URL or 127.0.0.1, or,
> 
>              If the pages you want to execute are not present,
>              rerun the ColdFusion installer to install the example
>              applications or documentation. Code examples that
>              you can run from the CFML Language Reference are
>              installed along with the example applications. 
> 
>             Note that for maximum security, you should not install
>             ColdFusion example applications or documentation on
>             a production server.
> 
> -----------------------snip--------------------------------------

Well, actually, this is a ColdFusion error, so .cfm templates are found 
and processed by CF Server correctly. But since documentation files are 
considered a security risk you can only run them from 127.0.0.1 by design.
If you create any other directories it should work just find, just not 
the cfdocs directory because that one is secured. The actual security is 
in the Application.cfm file so it propagates to subdirectories of 
/cfdocs, but you can remove it by deleting a few lines from the file.

Jochem


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with 
'unsubscribe' in the body or visit the list page at www.houseoffusion.com

Reply via email to