User-1643835564 posted
Consider the following scenario:
- In IIS Manager, under Default website (or any other websites), create a nested application "test" (i.e. the root of your application will be test)
- In the web.config for the sub application, configure the http platform installer.
If you visit http://localhost/test/ in your browser (the root of the child), then it tries to render the url /test/ from the proxied application. Given that we're viewing the root of the application, I'd have expected
it to proxy through to just / in the proxied application
The use case here is scenarios in which the same code may be deployed to a full website, or to a sub application. The current form means that the configuration of the http platform handler needs explicit knowledge of the path the code is deployed,
which makes deployments more complicated.
Two ways in which this could be fixed
- Update the module so that it proxies the url relative to the application root, rather than the full path of the url.
- Make the application root path avaialble in an environmental variable - that way we can handle the configuration through a set up script
