topic Re: Load HTTP WMS over HTTPS (using a proxy) in ArcGIS JavaScript Maps SDK Questions

Load HTTP WMS over HTTPS (using a proxy)

Raul_Jimenez — Mon, 04 Dec 2017 18:06:55 GMT

I have a problem trying to load a third party WMS (this one) over HTTP inside a Web AppBuilder app using HTTPs with popups enabled (via this Web map).

I have added a proxy (using the resource proxy) to the config.json and it seems to work (at first) as you will see here:

Every call to "ovc.catastro.meh.es" es been redirected though the proxy but then when the popup is triggered:

And if I edit the HTML directly it works:

Anyone know how to fix this? I'm not sure if this is an issue related to Web AppBuilder or to the ArcGIS API for JavaScript // cc: Jianxia Song, Lemao Wu, Robert Scheitlin, GISP, odoe

Thanks in advance!

Re: Load HTTP WMS over HTTPS (using a proxy)

RobertScheitlin__GISP — Tue, 05 Dec 2017 03:39:20 GMT

Raúl,

The first thing that comes to mind is that you attach an event listener for setFeatures on the maps popup and change the http url to https. I have never been in this situation so I can not give more details.

Re: Load HTTP WMS over HTTPS (using a proxy)

Raul_Jimenez — Tue, 05 Dec 2017 05:52:46 GMT

Thank's Robert!, let me try and I'll get back to you,

Re: Load HTTP WMS over HTTPS (using a proxy)

Raul_Jimenez — Sat, 11 Dec 2021 16:27:12 GMT

Thanks Robert!,

I finally made a change over the "server/apps/[APP_ID]/jimu.js/PopupManager.js" and inside the "initPopupMenu()" method I made these changes:

initPopupMenu: function(features){

        if(!features) {
          this._disablePopupMenu();
          this.popupMenu.setActions([]);
          return;
        }
        var featureSet = jimuUtils.toFeatureSet(features);

        // Adding proxy manually
        var proxyUrl = getAppConfig().httpProxy.rules[0].proxyUrl;
        var aux = proxyUrl + '?' + featureSet.features[0].attributes.QUERY_URL;
        featureSet.features[0].attributes.QUERY_URL = aux;
        // End changes

        ...        ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

So I just manually forced to replace the QUERY_URL attribute as a first approach and it worked.

Thanks!

Re: Load HTTP WMS over HTTPS (using a proxy)

RobertScheitlin__GISP — Thu, 07 Dec 2017 13:42:19 GMT

Raúl,

Don't forget to mark replies that help you get to correct answer as helpful.

Re: Load HTTP WMS over HTTPS (using a proxy)

FelixEscalas — Mon, 11 Dec 2017 13:58:20 GMT

I had the same issue than Raúl.

Forcing to use the proxy by changing the QUERY_URL attribute inside initPopupMenu has partially worked for us.

It works when you have only one WMS layer. But if you have two or more, when you click on the "Next feature" icon for the 2nd layer, the Mixed content error appears before initPopupMenu is called.

Do you have any suggestion?

Thanks in advance!

Re: Load HTTP WMS over HTTPS (using a proxy)

Raul_Jimenez — Tue, 12 Dec 2017 15:45:46 GMT

You're right Robert, done!, thx!

Re: Load HTTP WMS over HTTPS (using a proxy)

Raul_Jimenez — Tue, 12 Dec 2017 15:48:45 GMT

Hi Felix!,

I guess another method is called in that case. Have you tried inspecting the methods at PopupManager.js?

Cheers

Re: Load HTTP WMS over HTTPS (using a proxy)

FelixEscalas — Wed, 13 Dec 2017 09:03:52 GMT

Hi Raúl,

Nothing from PopupManager.js, the mixed-content error is fired before. I have little experience with the API, I can't find what is called when the "Next feature" button is pressed.

Best.

Re: Load HTTP WMS over HTTPS (using a proxy)

Raul_Jimenez — Fri, 22 Dec 2017 08:50:07 GMT

Sorry Felix I'm a little bit busy these days, I'll try to get back to your question asap, but let's see if Gavin Rehkemper, Lemao Wu or any Web AppBuilder experienced developer can help us here 😜

Re: Load HTTP WMS over HTTPS (using a proxy)

JunshanLiu — Fri, 22 Dec 2017 09:54:15 GMT

The httpProxy is used only if the request is sent by esri/request, but the URL in popup is not sent by esri request, so it does not go over the proxy.

So you'd better make your URL trusted by browser.

Re: Load HTTP WMS over HTTPS (using a proxy)

Raul_Jimenez — Fri, 05 Jan 2018 16:07:07 GMT

Thanks Junshan, /sorry I didn't see your message before, I should to check my notification settings on geonet ^_^'')

That's a good approach when the app is for internal use, but if they try to publish the app for the general public I guess that's not going to be enough, right?

I guess this is not using esri/request because it is been created through the webmap using the JS API and the createMap method, is that right? Could we fix it using the a proxy rule?

Thanks in advance! // cc: Bjorn Svensson Rene Rubalcava Justin Colville Jeremy Bartley

Re: Load HTTP WMS over HTTPS (using a proxy)

EugeneStaten — Wed, 14 Apr 2021 22:58:37 GMT

I have this same issue, except I am not using Web AppBuilder.

I am loading a public, wms layer over https via the proxy.

Here is the link:https://community.esri.com/t5/arcgis-api-for-javascript/wmslayer-bypasses-proxy-when-using-getfeatureinfo/td-p/1044417

Can any let me know what I can do in the WMS layer to make it work the same as here?

Re: Load HTTP WMS over HTTPS (using a proxy)

alegarma_dev — Wed, 06 Oct 2021 13:45:34 GMT

Hi Raul,

I have been trying to change this part of code in the PopupManager.js file after configuring my proxy in my IIS but I still come out with the same error (does not show the information in the popup)

What I have realised that when I make my screen smaller It partially works and goes through the proxy:

but not when I am using whole screen and does not show the popup correctly:

I will be pleased if you can give me any clue about this. Thank you

Re: Load HTTP WMS over HTTPS (using a proxy)

alegarma_dev — Thu, 21 Oct 2021 10:04:00 GMT

Hi,

I have found another possible solution (dangerous), that you can comment, modifying the featureInfoUrl value of the WMS layer in https://ago-assistant.esri.com/# from http to https.

I'm not an expert on this. I do not understand why featureInfoUrl goes throw http when the map is drawed in https? Now the popup works as I wished.

Best Regards,

Alex

Re: Load HTTP WMS over HTTPS (using a proxy)

Anonymous User — Fri, 22 Oct 2021 10:35:31 GMT

I also think in the WMSLayer, the popup’s iframe URL is created by appending values to the layer’s featureInfoUrl property. So maybe you can also fix it by altering the property after the layer has loaded.

Cheers!