I tried that and I got a 404 error instead.
The notification handler is StaticFile, so it seemed like the handler wasn't picking it up.
I re-verified that *.fwx was configured in Handler Mappings (and is Enabled) at the server level, but it was missing on the website level.
After adding it there, is started working.
-Paul
Sent by FoxWeb Support on 11/03/2015 01:01:24 PM:
The virtual directory is only necessary if you are planning to use old-style URLs that directly reference foxweb.exe or foxweb.dll. In your case you are using script mapped URLs with the fwx extension, so you may delete the virtual directory.
The errors you are getting are caused by the fact that you are using incorrect URLs. Assuming that the Virtual Program Root is correctly set to point to the sample scripts, the correct URL is http://localhost/ZipSearch/ZipSearch.fwx.
FoxWeb Support Team
support@foxweb.com email |
Sent by Paul Mrozowski on 11/03/2015 12:56:27 PM:
I installed FoxWeb on my Win 7 machine (which already had IIS and IIS 6 compat stuff installed). I created a virtual directory which points to C:\inetpub\scripts - that's where the foxweb.dll is located. I left the FoxWeb control center configured as default so the Default program root is C:\Users\Public\Documents\FoxWeb\Scripts. I am not running as a service.
I verified that the .FWX handler was set-up (both on the IIS level and on the virtual). When I try to hit any of the test scripts:
ex.
http://localhost/scripts/ZipSearch.fwx
or
http://localhost/scripts/ZipSearch/ZipSearch.fwx
I get this error:
| There was an error during the interpretation of your request |
| Message: |
|
The directory specified in the URL does not exist, or is inaccessible |
| |
The app pool is running 32-bit. I gave full permission to the ApplicationPoolIdentity that the website is running under to the C:\Users\Public\Documents\FoxWeb folder. I don't see any error messages in the ErrorLog.
What am I missing here?