View Complete Thread | FoxWeb Forum Home
Search:
Date:    Msg ID:   
From:    Thread:   
Subject:   
By html files I was referring to files that are intended to be served directly by the Web server, versus via a FoxWeb script.  Files that need to be accessed directly must reside in the Web tree.  Files that don't need to be accessed directly can (but don't have to) reside elsewhere.  The reason for recommending that all FoxWeb files reside outside the Web tree is that you don't want anyone downloading your PRG and/or data files.  Any file in the Web tree can be downloaded, by simply pointing to it in the URL.
 
FoxWeb can execute files in the FoxWeb Program Root and its sub-folders.  If a file is in a sub-folder, then you must make sure it include its path in the URL (e.g. http://servername/ContactMine2/contact.fwx).  All this information is included in detail in the FoxWeb documentation in the same page that I mentioned in my previous message (Locating and Addressing Scripts).
 
By the way, you mentioned that the folder name is "contactmine".  FoxWeb 2.X contains a folder named "ContactMine2".  The "ContactMine" sample script was included in FoxWeb 1.2X.  Which version of FoxWeb are you using?

FoxWeb Support Team
support@foxweb.com email

Sent by Tim Bowen on 05/27/2004 01:28:35 PM:
I seem to be making progress. I am wondering, the reading has me a bit confused, if I keep my prgs(fwxs) seperate from my htms & gifs, will that work fine? The html_out syntax line makes references to merging an htm, which is in a different location altogether.
2)
Under my c:\program files\foxweb\programs there are several folders one of which is called "contactmine". Within contactmine are the prgs. How does the web server know which folder to look at beyond the c:\program files\foxweb\programs folder?
 
 
Sent by FoxWeb Support on 05/26/2004 03:17:32 PM:
As I mentioned in my previous message, you should NOT associate the PRG extension with FoxWeb.  Your FoxWeb URLs should use the fwx extension, even though you are calling PRG files.  FoxWeb strips the extension and looks for the right file as described in the diagram below.
 
Please study the Locating and Addressing Scripts topic of the FoxWeb documentation carefully.  It provides detailed answers to your questions.  Here's a summary:
 
Recommended configuration:
  • Disable the Use Web Server's Directory Mappings option.
  • Set up the FoxWeb Default Program Root, so that it's outside your Web tree.  The Web tree is any location that can be accessed directly via your Web server (this includes the Web root, its sub-folders, as well as all folders defined as virtual roots in your Web server's configuration).  By default the Default Program Root is in C:\Program Files\FoxWeb\Programs, but you can change this in the FoxWeb Control Center.  If you want to use c:\inetpub\programs that's OK, as long as this location is not visible directly by your Web server (see below).
  • If you have only one virtual server listed in the FoxWeb Control Center, then let it use the Default Program Root.  In this case the Program Root column will simply display "[default]".  If you have multiple virtual servers, then you may want to configure different program roots for each of them.
  • Place FoxWeb scripts in the FoxWeb Program Root and its sub-folders.
  • Place your static files (html files, images, etc) in your Web root and its sub-folders.
  • If you are running FoxWeb with the VFP Run-Time DLL make sure that you have compiled your PRG files manually with the same version of VFP as what you chose when you installed FoxWeb.

The FoxWeb documentation describes how you can mix your scripts with static files and enable the Use Web Server's Directory Mappings option, but you need to be very careful, should you decide to go this route.  Please make sure to read the "Storing Scripts in the Web Tree" section of the Locating and Addressing Scripts topic, as well as the "Preventing your data and programs from being downloaded over the Web" section of the Securing your Server topic before attempting this.

 

FoxWeb Support Team
support@foxweb.com email

Sent by Tim Bowen on 05/26/2004 07:18:21 AM:
Ok, my foxweb has been running and NOT as a service either. I have the .prg  associated with c:\inetpub\scripts\foxweb.exe. I do not use fwx's. But I want to test this to see if it really works so my quest is    should "c:\inetpub\programs" contain my prgs and htm's?. I am confused about the 'DEFAULT PROGRAM ROOT'
 
Sent by FoxWeb Support on 05/25/2004 07:33:41 PM:
Have you started FoxWeb?  You need to do so, using one of the methods listed in the Operating the FoxWeb Server topic in the FoxWeb documentation (and in the readme file).  While you are setting up the server you should disable the Run as a Service option.  This will allow you to click on the FoxWeb tray icon and see the status of your channels, as well as view the actual channel windows (to look for potential problems).  You can view the channel windows by enabling the corresponding option in the FoxWeb Control Center and in the right-click context menu of the tray icon.
 
You should not associate prg files with foxweb.dll.  You can still call them using the fwx extension.  When a request gets received by FoxWeb (regardless of whether it contains the fwx script mapping, or explicitly points to foxweb.dll/exe), the software looks for fwx, prg and fxp files.  The following diagram describes this process:
 

 
 

FoxWeb Support Team
support@foxweb.com email

Sent by Tim Bowen on 05/25/2004 01:34:21 PM:
shoud l I associate the prgs with foxweb.dll as well?
I now get "could not connect to Foxweb broker"  when trying to go here:
 
I ask this, should my foxweb default program root which is "c:\inetpub\programs" contain my prgs and htm's?
and should I use web servers directory mappings?
 
 
 
 
Sent by FoxWeb Support on 05/25/2004 12:08:20 PM:
The readme.txt file in the FoxWeb directory contains instructions on testing a new FoxWeb installation.
 
By the way, I recommend associating the fwx extension with foxweb.dll instead of foxweb.exe.  The two programs offer identical functionality, but the dll uses the ISAPI protocol to communicate with the server, making it much more efficient, because the server does not need to start a new process with every request.

FoxWeb Support Team
support@foxweb.com email

Sent by Tim Bowen on 05/25/2004 10:14:16 AM:
I've gotten by that error and IIS 5.0 is running. I'v got both .prg & .fwx executable paths set to c:\inetpub\scripts\foxweb.exe. I have my htm files in c:\inetpub\wwwroot. How can I test this to see if it's actually works?
 
Sent by FoxWeb Support on 05/24/2004 10:51:09 AM:
This sounds like a configuration error.  I recommend that you initially disable the Run as Service option until you get FoxWe running properly.  Once you have fixed the problem, you can re-enable this option.
 
You should also check the file fwstart.log for any error messages that would help you identify the problem.

FoxWeb Support Team
support@foxweb.com email

Sent by Tim Bowen on 05/24/2004 08:19:48 AM:
Thanks, Is it normal not to be able to start my default web server until other foxweb components are configured correctly? I get the message "service did not respond to start or control request in a timely fashion".
 
Sent by FoxWeb Support on 05/21/2004 03:37:51 PM:
The Configuring your Web Server page in the FoxWeb documentation contains detailed instructions on how to configure IIS for use with FoxWeb.

FoxWeb Support Team
support@foxweb.com email

Sent by Tim Bowen on 05/21/2004 01:15:18 PM:
I've decided with other existing issues not to "migrate" but start again fresh. I have a clean IIS 5.0 on the new server and need to go to work setting it up. Can you point me to a good resource that explains all the IIS steps.?
Sent by FoxWeb Support on 05/16/2004 07:47:05 PM:
After installing FoxWeb you will have to copy all files from the FoxWeb Program Root and its subfolders from the old server to the same location on the new server.  The actual FoxWeb configuration would not take more than a couple of minutes if done manually, but I guess you could also export the old server and import it in the new server.  You can use regedit.exe, highlight hkey_local_machine\software\Aegis Group and select the File\Export menu option.  Copy the resulting reg file to the new server and double-click on it.
 
Regarding IIS, there is a utility that can copy Metabase information from one server to another, but I can't remember where I found it in the past.  It may be included in all IIS installations, but more likely I got it from the IIS Resource Kit.

FoxWeb Support Team
support@foxweb.com email

Sent by Tim Bowen on 05/13/2004 10:49:55 AM:
Can anyone advise on easiest way to move all I've got on my IIS 5.0/foxweb web server to new & different hardware? I've put so much configuration work into the current server that I'd hate to duplicate it manually. Thanks.