Support CORS for reconciliation endpoints #2260
The reconciliation CG is changing the standards to require CORS instead of JSONP (reconciliation-api/specs#19) so we should support CORS too. Ideally we would support both during a transition period. When trying to add a service, check first if it can be reached via CORS, then with JSONP. We should probably remember in the service manifest whether the service could be accessed via CORS or not, so that we avoid trying CORS and falling back to JSONP for all subsequent queries.