10:38:18 PM
3FV1CIU9C
Not sure, but you should check the web.config file in the folder of your app and make sure that the script map is actually there.
It's there - with the only entry being the script map I added:
<?xml version="1.0" encoding="UTF-8"?> <configuration> <system.webServer> <handlers> <add name="Aceweb" path="*.awp" verb="*" modules="IsapiModule" scriptProcessor="C:\inetpub\wwwroot\WConnect\wc.dll" resourceType="Unspecified" requireAccess="Script" preCondition="bitness32" /> </handlers> </system.webServer> </configuration>
But as mentioned, IIS does not recognize the mapping.
Also make sure that the folder supports script execution and that you allow the Web Connection ISAPI extension in that folder
Verified
If the app is tied to a single virtual you can also use the managed module which is easier to configure:
Can I do this by just replacing the above system.webServer section with your code below?
<system.webServer> <handlers> <validation validateIntegratedModeConfiguration="false" /> <add name="wc_wconnect" path="*.wc" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode" /> </handlers> <system.webServer>
The nice thing about the handler is that it doesn't have a path requirement - it picks up the module in the bin folder automatically. This means multiple scriptmaps can just be copied and added, then changing the path and name.
+++ Rick ---
This is on my development system running 64-bit Win 7. I have my app running in a virtual named WConnect with my .awp extension mapped to wc.dll I can make calls of the form localhost/wconnect/mymethod.awp and all works as expected.
I want to set the same mapping to the root folder so I can invoke methods without using the expanded path (i.e. localhost/mymethod.awp). I selected the Handler Mapping option under Default Web Site, added a script map for *.awp and pointed it to my dll. I made sure the "Invoke handler only if" box was clear and that all verbs were specified. But IIS does not seem to recognize the mapping. Any .awp call brings up a 404 error. The message indicates that the handler is "StaticFile"
We routinely configure our clients' systems so the app extension is mapped to the default directory, but for some reason I can't make it happen on my own machine. Any idea what I am missing?
--stein