Configurable Proxy Location for Maps in AGOL

[CharlieYe1]

Problem: AGOL uses a proxy (proxy.ashx) of its own, which is not configurable. This creates a protential problem to use AGOL out of box to access data sources where the proxy can't access.

We plan to use AGOL as our primary collaboration site for our geospatial professionals. One of the requirements is that internal users must be able to create and configure maps that use internal data sources. Since those data sources are hosted behind firewalls and not accessible from internet, any proxy.ashx hosted at AGOL will not work with those maps.

Proposed Solution:
1. Make a configuration for a default proxy.ashx Url for the whole AGOL organizational site.
2. Make the proxy Url configurable for each map. 
3. Make the proxy Url configurable for each layer in a map. 
 

[CharlieYe1]

Althrough we prefer all three stages of the solution to be implemented, but, the implementation of the first two stages should satisfy our needs. 

[AllanBenvin]

This would really make AGOL more flexible and work for organizations that have their own enterprise GIS.

[MikeAlfawicki]

This would really make AGOL more flexible and work for organizations that have their own enterprise GIS.

[AZendel]

Yes, please!  Our on-premises ArcGIS Server has a number of internally-produced cached maps. But to prevent external abuse of our cached maps, our AGS admins set up a proxy.  We can then configure apps to redirect to the proxy by editing their JavaScript code. But we can't do this with layers in web maps.  So we can't make a simple AGO Web map that has some points from an AGO feature service and our cached base map. Our only solution (that I'm aware of) is to make an app