- William Nevins
- PowerServer
- Thursday, 10 November 2022 02:29 PM UTC
When using IWA on an IIS website setup with a "Physical path" set to the project directory, IWA fails to load with a 404. The shortcut on our Windows desktop is:
"C:\Users\...\AppData\Local\Appeon\Appeon IWA Runner\AppeonIWAShell.exe" -r -u "https://mydomain.com/iwarunner.html"
When executed it is trying to load "https://mydomain.com/iwarunner.html/iwa.xml" instead of "https://mydomain.com/iwa.xml"
If we leave the IIS website "Physical path" to the root then it works. In that case the shortcut is:
"C:\Users\...\AppData\Local\Appeon\Appeon IWA Runner\AppeonIWAShell.exe" -r -u "https://mydomain.com/myapp/iwarunner.html"
When executed it loads "https://mydomain.com/myapp/iwa.xml"
How do we set it up so that the application is at "https://mydomain.com" instead of "https://mydomain.com/myapp"?
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.