You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently have my ArcGIS Server in a secured environment behind a firewall, and behind an API Gateway.
My API Gateway requires that I pass a token (myToken) to access resources. The layer allows me to set an ESRI token - that is not the issue here
The ESRI-Leaflet does not allow to add the API Gateway (myToken) token to the query string or body, or to set any kind of layer properties to add to the query string or body.
Normal convention would be to set in query string of URL parameter, therefore if i have the following URL property of the layer:
Resolved URLs, so that if a querystring parameter has been set, they are merged,
or (preferably)
have requestParam Object to the layer objects (feature, dynamic, tile etc) where the user can set such custom parameters, and the layer will either add as a querystring parameter (GET) or as body (POST).
ie: Chrome 51, IE11
L.version
):1.0.0?
L.esri.VERSION
):2.0.8,
master
?Steps to reproduce the error:
I currently have my ArcGIS Server in a secured environment behind a firewall, and behind an API Gateway.
My API Gateway requires that I pass a token (myToken) to access resources. The layer allows me to set an ESRI token - that is not the issue here
The ESRI-Leaflet does not allow to add the API Gateway (myToken) token to the query string or body, or to set any kind of layer properties to add to the query string or body.
Normal convention would be to set in query string of URL parameter, therefore if i have the following URL property of the layer:
https://abc.apigateway.com/server/rest/services/mapservice?mytoken=abc
The request fails, as the request being sent is:
https://abc.apigateway.com/server/rest/services/mapservice?mytoken=abc/export?
The ESRI leaflet plugin should either:
or (preferably)
I'm loading/bundling the library using:
webpack
The text was updated successfully, but these errors were encountered: