Using an IIS Reverse Proxy
Describes how to use Oxygen XML Web Author Component behind an IIS reverse proxy.
If you want to use Oxygen XML Web Author Component with IIS as a reverse proxy, follow this procedure:
- Configure IIS to allow double escaping in URLs. See the following examples:
- For Microsoft Azure, the applicationHost.xdt file should
contain the
following:
<?xml version="1.0" encoding="utf-8"?> <configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform"> <system.webServer> <security> <requestFiltering allowDoubleEscaping="true" xdt:Transform="SetAttributes(allowDoubleEscaping)" /> </security> </system.webServer> </configuration>
- For other types, insert the following fragment inside the
applicationHost.config
file:
<security> <requestFiltering allowDoubleEscaping="true"/> </security>
- For Microsoft Azure, the applicationHost.xdt file should
contain the
following:
- Configure Tomcat to allow escaped slashes. Append the following line in the
tomcat\conf\catalina.properties
file:
org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true - Set an environment variable to instruct Oxygen XML Web Author Component that the URL path
is already decoded. Insert the following line in the
tomcat\bin\catalina.bat
file:
set "URL_DECODING_PROXY=true"