You don't need to empty the fwx files -- you can simply delete them, or not copy them to the server in the first place. All you need is the FXP files.
In order to prevent a "page not found message" after you delete the fwx files (and also to prevent the same message when you call show_channels.fwx) you will need to disable the "Check that file exists" option in the script mapping configuration screen for the fwx extension.
Sent by Gabriel Badea on 04/27/2004 12:14:48 PM:
I've installed foxweb on Windows Server 2003 Small Business Server. Everything is fine and all is working wonderfully.
I do have a question however...
The server is a production server, (Microsoft ISA Server 2000 is also running on it), therefore I configured FoxWeb to run as a service and to use run-time dll's. (.fwx files are compiled manually on the beta server)
I then move the .fwx and the .fxp files on the production server, and I erase the contents .fwx file (not the file itself).
By doing this I prevent people from downloading my source code in the event that the server "looses" the script map that associates fwx files with the ISAPI module.
Is it OK to empty the .fwx or will I run into problems later on ?
Show_channels.fwx is not a "stand-alone" file distributed with the FoxWeb installer, therefore I assume it is included in the dll.
Say that the URL is www.actionproprio.com , then http://www.actionproprio.com/show_channels.fwx should work.
As a response I get the usual
The page cannot be foundThe page you are looking for might have been removed, had its name changed, or is temporarily unavailable.
How do I see the state of the channels in this case ?