[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-962) CORS Support
[ https://issues.oasis-open.org/browse/ODATA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-962: ----------------------------- Parent: ODATA-854 Issue Type: Sub-task (was: Improvement) > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]