-
Notifications
You must be signed in to change notification settings - Fork 21
Open
Description
Decided to deploy rdpx on ports 80 and 443 via IIS URL Rewriting so as not to disable other IIS based sites.
I used a proxy not for the root, but for /RemoteAppX (RAWeb is hosted in /RemoteApp and functions normally)
web.config from /RemoteAppX:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<rewrite>
<rules>
<rule name="ReverseProxyInboundRule1" stopProcessing="true">
<match url="(.*)" ignoreCase="true" />
<action type="Rewrite" url="http://127.0.0.1:8080/{R:1}" />
</rule>
</rules>
</rewrite>
</system.webServer>
</configuration>
UPD I found the reason (but not the solution):
Requests are coming in correctly.
In the HTML code of the response, the links go as if the proxy was running from the root directory "/".
I am looking for options for replacing the answer ...
IIS URL Rewriting: https://www.iis.net/downloads/microsoft/url-rewrite
Application request routing: https://www.iis.net/downloads/microsoft/application-request-routing
UPD: You can also suggest alternative solutions on how to get rdpx to work on IIS.
Metadata
Metadata
Assignees
Labels
No labels
