Select to view content in your preferred language

Remote Web Service without crossdomain file

968
7
06-17-2011 10:35 AM
MarkHuffman
Deactivated User
My Flex viewer needs to access a web service on a remote server (not ArcGIS Server). The server administrator does not want a crossdomain.xml file placed on that server. What are my options?
Tags (2)
0 Kudos
7 Replies
Drew
by
Frequent Contributor
My Flex viewer needs to access a web service on a remote server (not ArcGIS Server). The server administrator does not want a crossdomain.xml file placed on that server. What are my options?


You could probably re-route the web service by writing your own custom webservice that consumes the one you want, then you can control the crossdomain.xml file on your end.

so the architecture would look like...

Flex App -> Your Webservice -> Their web service

Drew
0 Kudos
HaroldBostic
Frequent Contributor
Similarly, you can make a request through a proxy, like the one esri has examples for.  That should work as well
0 Kudos
Drew
by
Frequent Contributor
Similarly, you can make a request through a proxy, like the one esri has examples for.  That should work as well


This is probably a better and simpler solution that mine 🙂
0 Kudos
MarkHuffman
Deactivated User
Thank you for your replies.

Is the proxy option the one referenced here? If so, that seems to apply to a remote ArcGIS Server service, which this is not.
0 Kudos
HaroldBostic
Frequent Contributor
Yes, but ArcGIS Server services are one use case.  for instance, the ArcGIS Flexviewer uses the proxy to access georss feeds.  you can access any type of webservice in the proxy page, you can access any url from the proxy page for that matter.
0 Kudos
MarkHuffman
Deactivated User
That's good to know.

Is this feature for Flex version 2.x only? It appears to be. If so, I will accelerate my upgrading plans.
0 Kudos
HaroldBostic
Frequent Contributor
Are you talking about georss feeds?  I'm not sure when the Viewer incorporated this functionality.

Accessing a webservice is a function of the proxy and not tied to any implementation of the web APIs
0 Kudos