AnsweredAssumed Answered

.NET proxy setup no longer working for WAB Dev 2.4

Question asked by brESRI on Mar 27, 2017
Latest reply on May 10, 2017 by rscheitlin

I have been using the proxy setup described by Robert Scheitlin here:

 

Internal ONLY Web Map Sharing Issues 

 

to get around AGOL logins for an internal-only, locally-hosted WAB Dev app that calls an AGOL Web Map.  I used username and password authentication.  The referenced Web Map is shared with my organization, and is not publicly available.

 

When I updated the app to WAB Dev 2.4, the proxy setup no longer works, and all I get is a blank (white) browser screen.

 

App config.json:

 

  "httpProxy":{

    "useProxy":true,

    "alwaysUseProxy":false,

    "url":"/DotNet/proxy.ashx",

    "rules":[{  
        "urlPrefix": "http://myorg.maps.arcgis.com/",  
        "proxyUrl": "/DotNet/proxy.ashx"  
    }]

},

 

proxy.config:

 

<?xml version="1.0" encoding="utf-8" ?>
<ProxyConfig allowedReferers="*"
             mustMatch="true">
    <serverUrls>
        <serverUrl url="http://myorg.maps.arcgis.com"
                   username="username"  
                   password="password"  
                   matchAll="true"/>  
        <serverUrl url="http://services.arcgisonline.com"  
                   matchAll="true"/>
        <serverUrl url="http://myinternalserver"  
                   matchAll="true"/>
    </serverUrls>
</ProxyConfig>

 

<!-- See https://github.com/Esri/resource-proxy for more information -->

 

Does anyone know how I can get the proxy working again?  The proxy is still working for my WD 2.3 apps on the same server.  I'm running ArcGIS Server 10.5.

Outcomes