A number of developers include the .prg, or .fxp extension in their URLs. In some of these cases the URL explicitly calls foxweb.exe (e.g. http://servername/scripts/foxweb.exe/myscript.fxp), while in others they manually configured their web server to associate the .fxp extension with foxweb.exe (e.g. http://servername/myscript.fxp). Assuming that the server is configured properly, both techniques will have the same result. FoxWeb 1.X simply strips the extension and runs the statement "DO myscript".
Sent by on 08/30/2006 05:49:13 AM:
Sorry I mis-stated the problem. The urls in the program reference the .fxp files directly.
We don't have a particular version of FoxWeb, I am just trying to figure out what we would have to do to make the program that we have run on a current version of FoxWeb.
Sent by FoxWeb Support on 08/29/2006 10:57:43 PM:
The ASP-like API and FWX files were not introduced, until FoxWeb version 2, which was release in 2001. Which version of FoxWeb do you have?
Sent by on 08/29/2006 05:47:41 AM:I have a question about a legacy program written in ~2000.
There are a bunch of reference to .fwx files in the URL's within the program, but the FoxWeb server does not seem to recognize these. Is the FoxWeb server's response to these files something that has changed in versions since then or was something done wrong?