[OASIS Issue Tracker] (ODATA-962) CORS Support

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64838#comment-64838 ] 

Michael Pizzo edited comment on ODATA-962 at 1/12/17 5:20 PM:
--------------------------------------------------------------

From 2017-1-12:
1) There is nothing specific to OData on CORS support
2) This would be good to put in the Implementing OData whitepaper
3) If we add a section on OPTIONS, as per OData-854, this would be a good place to call out CORS. Otherwise the most we could do would be a note in Protocol that just says services should be aware that they may need to support CORS, but that OData doesn't have any specific requirements on CORS over any standard REST service. 



was (Author: mikep):
If we add a section on OPTIONS, as per OData-854, this would be a good place to call out CORS.

> CORS Support
> ------------
>
>                 Key: ODATA-962
>                 URL: https://issues.oasis-open.org/browse/ODATA-962
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Sub-task
>          Components: OData URL Conventions
>    Affects Versions: V4.0_WD01
>            Reporter: Ramesh Reddy
>            Assignee: Michael Pizzo
>             Fix For: V4.01_CSD02
>
>
> When a client application is written in any of java script technologies like AngularJS, JQuery they use XMLHttpRequest. If they are doing a cross domain call to a OData service, they will be subjected to CORS, especially when any authentication is defined on the OData service.
> A good write up CORS can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
> Should OData as specification, recommend this to implemented on OData based services or leave it up to the service developer as implementation detail.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)