When IIS receives a request that does not contain a file name, it looks in the specified folder for any of the defined default names (default.htm, default.aspx, etc.) in order of precedence. If such a file is found, it is handled just as if it had been included in the URL.
If you have configured FoxWeb to use the Web server's directory mappings, then your scripts are already in the web tree (essentially your FoxWeb Program Root and the Web server root folder are one and the same), so it will all magically work.
If on the other hand you are using the default FoxWeb configuration, where you have separate folders for your FoxWeb scripts and your static files, then you will have to fool IIS into calling the script. All you need to do is create a file with the same name as the actual script and place it in the corresponding folder in your web tree. The file will not get used in any way, so it can be empty.
- Default script name: index.fwx
- Web root: c:\inetpub\wwwroot
- FoxWeb Program Root: c:\users\public\documents\FoxWeb\scripts
- Add index.fwx in the list of default document names in IIS Manager
- Place your actual index.fwx script in c:\users\public\documents\FoxWeb\scripts
- Place an empty file with the name index.fwx in c:\inetpub\wwwroot
- Calling http://servername/ should execute index.fwx, just as if you had called http://servername/index.fwx.
|FoxWeb Support Team
Sent by Steve Moore on 08/03/2013 10:59:09 PM:
Does anyone know if there is a way to use a foxweb script as a default document in IIS7. That is to say I want to call a foxweb script in place of "index.html" when the root domain is requested (i.e., www.mydomain.com/). I know I can place a redirect in an html page but I don't think google would like that...
So is there any way to make IIS call a script directly, ie map a script to a domain default document?
Thanks in advance for any suggestions.