You are using the older method of addressing FoxWeb scripts in the URL, where instead of taking advantage of script mappings you are directly referencing foxweb.exe. This is fine, but it does require additional setup for IIS.
First of all you will need to make sure that FoxWeb is correctly setup with script mapping configuration (just because most of the required setup is done by the setup program and it's a subset of the configuration you need to have in place anyway).
Try calling the following:
https://<our web site>/show_cgi.fwx
Does this work or do you get an error? If there's an error, make sure that you have installed the IIS features and configured the permissions listed in the Configuring your Web Server page. You will also need to make sure that you have configured the application pool to run 32-bit modules.
Once you have script mapping working properly, you will need to add a Scripts virtual folder, pointing to the location where foxweb.exe and foxweb.dll were installed, and configure it for CGI access. By default this location is C:\Program Files (x86)\FoxWeb\CGI.
You may also have to enable the CGI-exe handler mapping.
FoxWeb Support Team
Sent by Art Bergquist on 06/12/2015 12:02:52 PM:
OK, got IIS 7.5 set up on Windows 2008 Server. Started IIS and FoxWeb.
Employing the hosts file re-direction technique, we can bring up the new web site on a particular machine while allowing the current (hopefully, soon-to-be-old) web site to continue to be up and running for our 24-7 operation.
The anonymous part of the new web site comes up fine. When I go to our login web page (https://<our web site>/login.shtml, it also appears fine. When I enter my correct user id and password and click on [Login], it goes to https://<our web site>/scripts/foxweb.exe/<name of .FWx file> but displays the following error:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
The Default program root: is the same on the Virtual Servers tab in the FoxWeb Control Center on both the Windows Server 2003 and Windows Server 2008 servers.
In comparing all IIS 6 settings on Windows Server 2003 vs. all IIS 7 settings on Windows Server 2008 and all settings in the FoxWeb Control Center on both machines, everything appears to be in order.
Am I missing something obvious and/or where should I be looking to resolve this issue?
Sent by FoxWeb Support on 05/17/2015 12:48:09 PM:
Your understanding and plan on migrating the site from the old to the new server is correct.
I would definitely recommend using relative URLs, rather than absolute or fully qualified URLs. If you are currently using fully qualified URLs, containing the host name, then you will need to update them before being able to address your new server by IP address.
You will need to enter the IP address in the IP Address column of the virtual servers page. Once you are done with testing and want to migrate your site, you will need to enter the host name in the Server Name column.
FoxWeb Support Team
Sent by Art Bergquist on 05/16/2015 12:52:38 PM:
Also, would I enter the IP address (e.g., 184.108.40.206) as the Server Name on the new server on the Virtual Servers tab of the FoxWeb Control Center to temporarily test the new web site?
Sent by Art Bergquist on 05/16/2015 11:21:19 AM:
I'm in the process of migrating a FoxWeb web site from Windows Server 2003 (which, of course, is about to be no longer supported by Microsoft) to Windows Server 2008. The Windows Server 2008 has already been set up and I can access it via RDC.
The (current) web site is 24-7 so the client wants the ability to first test the new web site on Windows Server 2008 while still running it (i.e., maintain uptime) on Windows Server 2003. The new web server (Windows Server 2008) already has access to a copy of the database on it (via mapped drives to a new database server) so that it would interact with the new database; as a result, it's a totally separate (encapsulated/isolated) environment.
It's my understanding that we could (temporarily) refer to the new website with its IP address; for example, if the new server's IP address is 220.127.116.11, then we could test the new web site by going to the following URL:
Once we're satisfied that the new web site (on Windows Server 2008) works as well (or better) than the current web site (on Windows Server 2003), then we would have to transfer the domain (i.e., the user-friendly name of the web site) from the current (Windows Server 2003) to the new (Windows Server 2008).
1. Is the above correct? (If not, feel free to correct how I'm wording the scenario as well; I want to not only solve this issue but also to state it correctly as well.)
2. Also, per the "Locating and Addressing Scripts" FoxWeb help topic, I'm thinking that it would be a good idea to first switch all the URLs within the FoxWeb web site (except for the main web page) from Fully Qualified URLs to Relative URLs. Would you also recommend that?