In my current project we have hosted the ESRI JS API within the organisation's IIS.

For most of the part the deployed application works fine, but we notice that certain calls are being made to https://js.arcgis.com despite the corresponding JS files being present in the local deployment.

I have deployed the ESRI API as per instructions within their readme/install documentation. I have not completed the steps under "Change the ArcGIS Services Directory "View In JavaScript" URL" section, as I think these are optional and only apply when viewing the deployed map services from within the REST services directory.

Any ideas why the external calls are being made?

enter image description here

  • Is the "deployed application" your own custom built app? Or something provided by esri or someone else? – Bjorn Svensson Nov 29 '18 at 7:20
  • This is a custom GIS application utilizing ESRI's JS API – ujjwalesri Nov 29 '18 at 7:22

Okay...so I eventually figured out why it was behaving like that.

Apparently, the URL changes had not been done one the particular instance and it was reading the original copy deployed within the 'js' folder and not the locally deployed one.

When we began the development, we were not using the locally deployed ESR JS API, and later in the development phase we switched to it. The setting for some reason remained unmodified for this environment.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.