View Complete Thread | FoxWeb Forum Home
Search:
Date:    Msg ID:   
From:    Thread:   
Subject:   
We don't recommend that you make your Program Root or any of its subdirectories accessible over the Web, because this will allow downloading of any file in these directories, including data files.

Should you decide to keep your program and web directories in the same location you should enable the Use Web Server's Directory Settings option in the FoxWeb configuration.  Before making this decision, I advise you to study the the concepts and security implications described in the Locating and Addressing Your Scripts chapter of the FoxWeb documentation.

FoxWeb Support Team
support@foxweb.com


Sent by Alan Harris-Reid on 12/22/2001 08:24:29 PM:

I've had to restructure my virtual directory structure and it is now as follows...

localhost (web root folder c:\inetpub\wwwroot)
   MyWebSite (virtual folder - mapped to FoxWeb program root)
      Data      (real subfolder of program root)
      Graphics  (real subfolder of program root)
      Progs     (real subfolder of program root)
      Scripts   (real subfolder of program root)

When I type "http://localhost/MyWebSite/scripts/MyScript.fwx" in the browser I get the following error message...

"There was an error during the interpretation of your request.
Message:  The directory specified in the URL does not exist, or is inaccessible"

I've checked the following...
IIS and Foxweb are definitely running
The URL directory definitely exists, because if I substitute MyPage.htm for MyScript.fwx (both files exist in the scripts folder) the html page displays fine.
Execute permissions are set to "scripts only" for the MyWebSite virtual folder.
The .fwx extension is mapped to foxweb.dll.

Now, here's the real wierd thing - if I type http://localhost/scripts/myscript.fwx (ie. omitting the MyWebSite virtual folder), the script runs, but without any images displaying (because the relative path instructions expect a graphics folder in parallel with scripts).
The Scripts subfolder of localhost is in fact c:\inetpub\scripts, which is where myscript.fwx definitely does NOT exist, so it's a mystery why it runs at all from this address.

Any help would be appreciated.

Alan Harris-Reid