Problem/Limitation in using flXHR

I had a cross domain issue and after browsing for a while i came across flXHR which seemed to be promising solution and hence i went ahead with it. It's a flash based cross domain solution which is based on a crossdomain.xml config file (which lists the list of sites from where you can access the services). For more details on flXHR click here.

I thought I have the great solution in hand and work with it before I encountered thee major of limitation of flXHR: 
The location of crossdomain.xml can be specified in configuration of flproxy via loadPolicyURL attribute. Which is supposedly the path flXHR will take to resolve the permission of your domain to access service hosted at that domain.
However this is where the problem comes it will not only consider the crossdomain.xml at given location but it will also make a query at the root of the site and hunt gain for crossdomain.xml to see the permission for the client domain to access the service e.g. if you specify flXHR lib will still hunt for crossdomain.xml at if your crossdomain is not hosted at this place your call won't be successful.

Although this scenario is rare but in case you couldn't host your crossdomain.xml @root or your root redirects somewhere else flXHR won't be of your use.


Popular posts from this blog Connection reset

Hide empty last column from Table/Tree Viewer

Spring: implements interface not working in @Controller