As described in our Geospatial Product Help, there may be circumstances where you want or need to use a proxy for the ESRI server. For example, you might have security tokens that you do not want to be visible on your local ESRI server. Or you may have requests that exceed the limit on the length of the uniform resource locators (URLs) imposed by the browser. Or you may have CORS limitations on the local ESRI server.
Using a proxy for the ESRI server can get around all these problems. However, if your local ArcGIS server resides “behind” the WAF (web application firewall) and the web container such as Tomcat (running the ArcGIS web adaptors) requires the Basic Auth, using the access token in the
esriproxy.jspwill not pass the authentication.
<serverUrl>entry for each service that will use the proxy. The
proxy.configallows you to use the serverUrl tag to specify one or more ArcGIS Server services that the proxy will forward requests to. The serverUrl tag has the following attributes:
trueall requests that begin with the specified URL are forwarded. Otherwise, the URL requested must match exactly.
true, the IIS application pool identity will be used for authenticating with secured resources. This configuration will supersede the domain, username, and password configurations. The default is
false. Only applies to DotNet proxy.
urlproperty and that should be redirected. Example:
<serverUrl url="http://fakedomain" hostRedirect="http://172.16.85.2"/>.
Note: Refresh the proxy application after updates have been made to
proxy.config
<serverUrl url="http://route.arcgis.com"
clientId="6Xo1d-example-9Kn2"
clientSecret="5a5d50-example-c867b6efcf969bdcc6a2"
rateLimit="600"
rateLimitPeriod="60"
matchAll="true">
</serverUrl>
<serverUrl url="http://sampleserver6.arcgisonline.com/arcgis/rest/services"
matchAll="true">
</serverUrl>