OASIS Open Data Protocol (OData) TCIcon indicating the project type

OASIS Open Data Protocol (OData) TC

Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-854 Consider use of OPTIONS for discovering formats, other capabilities and features
  3. ODATA-962

CORS Support

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: V4.0_WD01
    • Fix Version/s: CN01
    • Component/s: Implementing OData
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          mikep Michael Pizzo (Inactive) added a comment - - edited

          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.

          Show
          mikep Michael Pizzo (Inactive) added a comment - - edited 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.
          Hide
          Permalink
          ralfhandl Ralf Handl added a comment - - edited

          Cloned to https://github.com/oasis-tcs/odata-specs/issues/282

          Show
          ralfhandl Ralf Handl added a comment - - edited Cloned to https://github.com/oasis-tcs/odata-specs/issues/282

            People

            • Assignee:
              martinzurmuehl Martin Zurmuehl
              Reporter:
              rareddy Ramesh Reddy
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: