Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Redirecting ISAPI app
#1
I had no problem with deploying app on IIS, as long as I'm connecting to "http://#.#.#.#/virtualdir/app.dll", application works.

How to configure IIS to call my app as "http://#.#.#.#/alias" ?

I followed instruction provided by atozed:  http://docs.atozed.com/docs.dll/deployme...20IIS.html  but without success.
I made required changes to ServerController.OnConfig() 

All I get is error:

Detailed Error Information:
Module   IIS Web Core
Notification   MapRequestHandler
Handler   StaticFile
Error Code   0x80070002
Requested URL   http://localhost:80/Features/
Physical Path   C:\inetpub\wwwroot\Features\
Logon Method   Anonymous
Logon User   Anonymous
Reply
#2
The easiest way is to set up a redirect from the URL you want to the app starting URL. You can do this in IIS, or even using a simple index.html that redirects in the location.

You may also consider http.sys which uses the same core as IIS and is not only more flexible, but far easier to deploy and debug.
Reply
#3
IIS is enduser requirement, and index.html as redirector leaves ugly working path: "host/virtualdir/app.dll" exposed.
I knew documentation for Intraweb is rather skimpy but I had hope docs provided @https://doc.atozed.com/en/ are accurate.
Reply
#4
They are accurate. The problem is that MS like their other products keeps changing stuff often for no good reason other than to change the UI so the docs may not exactly match your IIS version.

You can also use ASPX deployment on IIS which doesnt show .dll, but that being said you can use URL Rewrite as you are currently seeking.

Alexandre will need to follow up further.
Reply
#5
(04-14-2021, 05:40 PM)TinyCthulu Wrote: IIS is enduser requirement, and index.html as redirector leaves ugly working path: "host/virtualdir/app.dll" exposed.
I knew documentation for Intraweb is rather skimpy but I had hope docs provided @https://doc.atozed.com/en/ are accurate.


The documentation for the URLRewrite is correct and the feature works correctly as described. This is being used by many customers and has been extensively tested.

Given the error message, I would guess that your configuration is wrong. Is that your physical path?
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)