topic Re: Proxy problems in ArcGIS JavaScript Maps SDK Questions

Proxy problems

MKF62 — Fri, 10 Dec 2021 20:17:23 GMT

I'm quite confused on how to get this proxy working.

I've secured one geoprocessing service called Habitat Management. It is located in the HabitatManagement folder, the service is titled HabitatManagement, and it contains a geoprocessing task called HabitatManagement. Essentially, the url for the secured service looks like this:

https://www.mydomain.com/myServer/rest/services/HabitatManagement/HabitatManagement/GPServer/HabitatManagement

The actual web mapping application resides inside of a .NET application. The URL of the .NET application is this:

https://www.mydomain.com/appName

The actual web map url is this:

https://www.mydomain.com/appName/HabitatMap/HabitatJSMap

I have my proxy config file set up like so:

<ProxyConfig allowedReferers="https://www.mydomain.com/appName/*"
             mustMatch="true"
             logFile="proxyLog.txt"
             logLevel="Warning">
    <serverUrls>
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatManagement/"
                  username="username"
                  password="password"
                  matchAll="true"/>
    </serverUrls>
</ProxyConfig>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I have the proxy JS code like this:

urlUtils.addProxyRule({
                urlPrefix: "https://www.mydomain.com",
                proxyUrl: "https://www.mydomain.com/appName/proxy/proxy.ashx"
            });‍‍‍‍‍‍‍‍

If I go to the proxy page following this URL:

https://www.mydomain.com/appName/proxy/proxy.ashx

It works as expected, it says "Config File: "OK" Log File: "OK""

When I test this URL, it takes me to the HabitatManagement folder but does not show the services within it, even though the token should be passing the username and password so I can see the services, right? That's issue #1 that I don't understand.

https://www.mydomain.com/appName/proxy/proxy.ashx?https://www.mydomain.com/myServer/rest/services/HabitatManagement

Additionally, when I go the web map and try to access the service, it still makes me login with this message:

Please sign in to access the item on https://www.mydomain.com/myServer (HabitatManagement/HabitatManagement)

If I login, things work fine - it appears the token is generated and appended to the URL as it should be.

If I change the config file serverURL to this (note the extra "HabitatManagement" on the end of the URL):

<serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatManagement/HabitatManagement"
                  username="username"
                  password="password"
                  matchAll="true"/>‍‍‍‍‍‍‍‍‍‍‍‍

and try this URL, the request fails with "Bad Request" error:

https://www.mydomain.com/appName/proxy/proxy.ashx?https://www.mydomain.com/myServer/rest/services/HabitatManagement/HabitatManagement

and if I test it in the application it still prompts me to login with the same message as before.

I have also tried to change my serverURL to something very general with no luck. Ideally, the serverURL would be more specific than this as there are some services we have that don't require authentication thus do not need to run through a proxy.

<serverUrl url="https://www.mydomain.com"
                  username="username"
                  password="password"
                  matchAll="true"/>‍‍‍‍‍‍‍‍

I'm not sure if my proxy is located in the wrong spot, or if my referrer URL is messed up, or if my serverURLs are messed up. How do I access my secured services using the proxy?

Re: Proxy problems

RobertScheitlin__GISP — Tue, 23 Oct 2018 15:58:20 GMT

Molly,

For testing purposes change your allowedReferers to: allowedReferers="*" I also always define the proxy using esriConfig:

require(["esri/config"], function(esriConfig) {

esriConfig.request.proxyUrl = "/resource-proxy/Java/proxy.jsp";

});

Re: Proxy problems

MKF62 — Tue, 23 Oct 2018 16:35:52 GMT

I have since tried setting the allowedRefers to a wildcard but still am having issues.

The documentation states that I should be used the addProxyRule given that I am using a username and password:

Using the proxy | Guide | ArcGIS API for JavaScript 3.26

Note: If you are storing login information (username and password or client_id and client_secret) in the proxy you will want to use the addProxyRule option so that requests to the resources with the specified URL prefix are routed through the proxy.

If I change it to esriConfig.request.proxyUrl would it be equal to this? "/proxy/proxy.ashx"

I am using the .NET installation of the proxy and the folder it sits in I have renamed as "proxy"

Re: Proxy problems

RobertScheitlin__GISP — Tue, 23 Oct 2018 16:41:30 GMT

Molly,

I use a single proxy for my whole web server so normally my proxy url is not using a relative path, but a full path like:

esriConfig.request.proxyUrl = "https://www.mydomin.com/proxy/proxy.ashx";

Re: Proxy problems

MKF62 — Tue, 23 Oct 2018 16:52:33 GMT

Thanks, just tried it, but it didn't do the job (going off the documentation for defaults.io syntax)

esriConfig.defaults.io.proxyUrl = "https://www.mydomain.com/appName/proxy/proxy.ashx"

Re: Proxy problems

RobertScheitlin__GISP — Tue, 23 Oct 2018 16:54:34 GMT

Molly,

defaults.io is for 3.x I thought you were using 4.x..?

Re: Proxy problems

MKF62 — Tue, 23 Oct 2018 17:31:02 GMT

Nope. I had to switch to 3.24 a while back because 4.x didn't have file upload capabilities yet.

Re: Proxy problems

RobertScheitlin__GISP — Tue, 23 Oct 2018 17:35:16 GMT

OK,

So with the above url to your proxy.. That means that your proxy folder is under (inside of) your apps folder then?

https://www.mydomain.com/appName/proxy/proxy.ashx

Re: Proxy problems

MKF62 — Fri, 10 Dec 2021 20:17:26 GMT

Yes - you are correct. The "proxy" folder is located underneath my app folder.

I have tried a new combination of Urls and now I'm getting a little closer... now I can access my services by going direct with the URL without having to login. I can see that it logs me in with the correct user that I have allowed access to the secured service.

https://www.mydomain.com/appName/proxy/proxy.ashx?https://www.mydomain.com/myServer/rest/services/HabitatManagement/HabitatManagement/GPServer/HabitatManagement

This occurs when I use this configuration:

//Set up the proxy to forward requests for data/geoprocessing tools
            urlUtils.addProxyRule({
                urlPrefix: "https://www.mydomain.com",
                proxyUrl: "/proxy/proxy.ashx"
            });‍‍‍‍‍

<ProxyConfig allowedReferers="https://www.mydomain.com/*"
             mustMatch="true"
             logFile="proxyLog.txt"
             logLevel="Warning">
    <serverUrls>
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatManagement/HabitatManagement/GPServer/HabitatManagement"
                 username="username"
                 password="password"
                 matchAll="true"/>
    </serverUrls>
</ProxyConfig>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

If I go to my service in the web map, it still wants me to login and gives me an error about the token being required in the POST request header.

{"error":{"code":499,"message":"Token Required","details":[]}}

Re: Proxy problems

RobertScheitlin__GISP — Tue, 23 Oct 2018 18:40:29 GMT

Molly,

This is because you are providing credentials only when it is going to the GP service url and nothing when it is going to the web map. Add a serverUrl for your web map to the proxy.config. https://www.mydomain.com/appName/HabitatMap/HabitatJSMap

Re: Proxy problems

MKF62 — Fri, 10 Dec 2021 20:17:28 GMT

Have added it. Now prompting me to log in to view the data on the map, so it's still not generating a token for some reason.

<ProxyConfig allowedReferers="https://www.mydomain.com/*"
             mustMatch="true"
             logFile="proxyLog.txt"
             logLevel="Warning">
    <serverUrls>
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatManagement/HabitatManagement/GPServer/HabitatManagement"
                 username="username"
                 password="password"
                 matchAll="true"/>
      <serverUrl url="https://www.mydomain.com/appName/HabitatMap/HabitatJSMap"
                 password="username"
                 password="password"
                 matchAll="true" />
    </serverUrls>
</ProxyConfig>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Getting a 404 Resource Not Found error. I wonder if it's because I have a relative path as my proxy path?

It says this, so that might be it:

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested URL: /proxy/proxy.ashx

The URLs it's trying to place a request with also are off:

https://www.mydomain.com/proxy/proxy.ashx?https://www.mydomain.com/myServer/rest/services/…

I wonder if I change the JS to this if it would work? Or may make the proxyUrl property an absolute path instead of relative. I will play around with it.

//Set up the proxy to forward requests for data/geoprocessing tools
            urlUtils.addProxyRule({
                urlPrefix: "https://www.mydomain.com/appName/HabitatMap/HabitatJSMap",
                proxyUrl: "/proxy/proxy.ashx"
            });‍‍‍‍‍

Re: Proxy problems

RobertScheitlin__GISP — Tue, 23 Oct 2018 18:58:23 GMT

Molly,

Are there secured service in the map? Are you using an WebMap from AGOL or Portal?

Re: Proxy problems

MKF62 — Tue, 23 Oct 2018 19:02:25 GMT

Just edited my answer above, but yeah, the MapServer data is secured as well as one other GP service than the one already mentioned, so that's why I'm getting a login page for the whole map now. I could turn security off for those services and just leave the one aformentioned GP service secured and see what happens.

Re: Proxy problems

RobertScheitlin__GISP — Tue, 23 Oct 2018 19:03:50 GMT

No need for that just add serverUrls for each secured service to the proxy config.

Re: Proxy problems

MKF62 — Fri, 10 Dec 2021 20:17:31 GMT

Alright. I have all the services in the config file. Now, no login prompts, however no data on the map either. I am getting a lot of "resource not found" in the console.

Network tab snippet:

When I go look in the header and response for details, this is in the response:

<H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1>
<h2> The resource cannot be found. </h2>

 Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
 
 Requested URL: /proxy/proxy.ashx

So it seems like it can't find the proxy URL which suggests that my JS code needs to be altered in some way, right? I changed my proxyUrl to be an absolute path but that has not changed anything.

//Set up the proxy to forward requests for data/geoprocessing tools
            urlUtils.addProxyRule({
                urlPrefix: "https://www.mydomain.com/",
                proxyUrl: "https://www.mydomain.com/appName/proxy/proxy.ashx"
            });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I have also tried this because I'm not entirely sure what the urlPrefix does:

//Set up the proxy to forward requests for data/geoprocessing tools
            urlUtils.addProxyRule({
                urlPrefix: "https://www.mydomain.com/appName",
                proxyUrl: "/proxy/proxy.ashx"
            });
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Given where the proxy sits in the application, I think the proxy would be located at https://www.mydomain.com/appName/proxy/proxy.ashx. The proxy folder sits under the root folder "appName" in my visual studio solution explorer which creates all the URLs and what not.

Re: Proxy problems

RobertScheitlin__GISP — Tue, 23 Oct 2018 19:25:46 GMT

Molly,

Can you show me the serverUrl url that you added for your secure service (replacing sensitive info, but not over doing it)? It sounds like it is not the proxy url that it can't find but the map service url.

Re: Proxy problems

MKF62 — Fri, 10 Dec 2021 20:17:34 GMT

My bad, I didn't publish my app quite right after changing the JS, so I redid it and now I get the log in prompt again (no "resource not found" errors). Just to clarify everything...

Current JS:

//Set up the proxy to forward requests for data/geoprocessing tools
            urlUtils.addProxyRule({
                urlPrefix: "https://www.mydomain.com/appName",
                proxyUrl: "/proxy/proxy.ashx"
            });
‍‍‍‍‍‍‍‍‍‍‍

Current config:

<ProxyConfig allowedReferers="https://www.mydomain.com/*"
             mustMatch="true"
             logFile="proxyLog.txt"
             logLevel="Warning">
    <serverUrls>
      <serverUrl url="https://www.mydomain.com/appName/HabitatMap/HabitatJSMap"
                 username="username"
                 password="password"
                 matchAll="true" />
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatManagement/HabitatManagement/GPServer/HabitatManagement"
                 username="username"
                 password="password"
                 matchAll="true"/>
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer/0"
                 username="username"
                 password="password"
                 matchAll="true" />
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer/1"
                 username="username"
                 password="password"
                 matchAll="true" />
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer/2"
                 username="username"
                 password="password"
                 matchAll="true" />
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer/3"
                 username="username"
                 password="password"
                 matchAll="true" />
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer/4"
                 username="username"
                 password="password"
                 matchAll="true" />
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer/5"
                 username="username"
                 password="password"
                 matchAll="true" />
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatClassification/GPServer/HabitatClassification"
                 username="username"
                 password="password"
                 matchAll="true" />
    </serverUrls>
</ProxyConfig>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Proxy problems

RobertScheitlin__GISP — Fri, 10 Dec 2021 20:17:37 GMT

Molly,

OK you only have to have a serverUrl for each unique map service not each layer in the map service:

<serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer"
  username="username"
  password="password"
  matchAll="true"/>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

and reset your proxy rule to:

            //Set up the proxy to forward requests for data/geoprocessing tools
            urlUtils.addProxyRule({
                urlPrefix: "https://www.mydomain.com",
                proxyUrl: "/proxy/proxy.ashx"
            });‍‍‍‍‍

Re: Proxy problems

MKF62 — Fri, 10 Dec 2021 20:17:40 GMT

Back to "resources not found" errors when trying to load the map services. No log in window.

GET https://www.mydomain.org/proxy/proxy.ashx?https://www.mydomain.org/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer/1?f=json 404 (Not Found)

Config:

<ProxyConfig allowedReferers="https://www.mydomain.com/*"
             mustMatch="true"
             logFile="proxyLog.txt"
             logLevel="Warning">
    <serverUrls>
      <serverUrl url="https://www.mydomain.com/appName/HabitatMap/HabitatJSMap"
                 username="username"
                 password="password"
                 matchAll="true" />
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatManagement/HabitatManagement/GPServer/HabitatManagement"
                 username="username"
                 password="password"
                 matchAll="true"/>
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer"
                 username="username"
                 password="password"
                 matchAll="true" />
      <serverUrl url="https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatClassification/GPServer/HabitatClassification"
                 username="username"
                 password="password"
                 matchAll="true" />
    </serverUrls>
</ProxyConfig>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

JS:

//Set up the proxy to forward requests for data/geoprocessing tools
            urlUtils.addProxyRule({
                urlPrefix: "https://www.mydomain.com",
                proxyUrl: "/proxy/proxy.ashx"
            });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Would the way the feature layers are defined possibly pose a problem? I swear I've seen people having trouble with definition expressions and proxies for some reason. Granted I don't know why that would produce 404 errors. Seems unlikely.

 //Add the habitat patches feature layer
            var patchesFL = new FeatureLayer("https://www.mydomain.com/myServer/rest/services/HabitatMonitoring/HabitatData/MapServer/2", {
                mode: FeatureLayer.MODE_ONDEMAND,
                autoGeneralize: false,
                refreshInterval: 10,
                visible: false,
                infoTemplate: patchesPopupBox,
                outFields: ["*"]
            });
            patchesFL.setMinScale(500000);
            patchesFL.setSelectionSymbol(selectionSym);
            patchesFL.setDefinitionExpression('ReportingYear = ' + currentYear);‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Proxy problems

RobertScheitlin__GISP — Tue, 23 Oct 2018 20:34:23 GMT

Molly,

It appears that the proxy url is not defined correctly based on the error:

https://www.mydomain.org/proxy/proxy.ashx? It seems to be missing the appName portion of the url.