Esri / resource-proxy

Proxy files for DotNet, Java and PHP.
Apache License 2.0
371 stars 322 forks source link

preliminary calls not using proxy #564

Closed cdempewolf closed 1 year ago

cdempewolf commented 2 years ago

We have an application that is configured to use the .net proxy. We are seeing some of the preliminary calls fail to use the proxy, which results in them giving an error. We are using the proxy for authentication, but also to map to an internal server from a public load balancer. There are two calls that are not using the proxy, and when on an external server they return failures. How can we ensure that these calls utilize the proxy correctly?

[serverURL]/arcgis/rest/services/[serviceName]/MapServer/?f=json&callback=jQuery203092935758371764731640207000238&=1640207000239

[serverUrl]/arcgis/rest/info?f=json

bsvensson commented 2 years ago

Hi @cdempewolf - If the application isn't sending the requests to the proxy for some use cases, then it sounds like the problem is with the application - not with the resource proxy.

cdempewolf commented 2 years ago

I appreciate your quick response. However, part of the problem that we're seeing is that these calls are not ones that the code is making explicitly. We can find no origination for them, and the proxy is configured to intercept all traffic to these servers before the calls are sent over. So these calls should be intercepted by the proxy, but for some reason are not using the proxy rules defined.

bsvensson commented 2 years ago

With "application", I meant any request coming from the application when used in the browser, whether it's specifically the application code or some other library used by the application.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you need additional assistance please contact Esri Technical Support. Thank you for your contributions.

github-actions[bot] commented 1 year ago

This issue has been automatically closed due to inactivity. If you need additional assistance please contact Esri Technical Support.