1

In order to be able to do cross-domain AJAX requests, SharePoint 2013 introduced SP.RequestExecutor.js library which uses a hidden iframe to do the request.

This looks hacky (although I'm not sure if it actually is) and is different from the developers who never used SharePoint before are accustomed to.

Why not using the standard way which relies on CORS (which is actually the recommended standard of the W3C)?

Since the cross-domain requests are done between applications handled by SharePoint, it seems natural to provide and use CORS under the hood, transparently (allowing to configure Access-Control-Allow-Origin header within SharePoint 2013 Central Administration).

closed as primarily opinion-based by Robert Lindgren Apr 3 '15 at 18:25

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

1

I think it would be difficult for someone outside of the product team to give an accurate reason as to why they implemented this using a technology other than CORS... I would guess that in addition to any technical reasons though, CORS was not a reommended standard until January 2014, pre-dating the implementation of the App Model and SharePoint 2013.

Not the answer you're looking for? Browse other questions tagged or ask your own question.