Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-813 Allow no metadata for non-OData clients
  3. ODATA-861

Define behavior when neither accept header or $format query parameter is specified

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.0_ERRATA02
    • Fix Version/s: V4.0_ERRATA03
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      Applied

    • Proposal:
      Hide

      Clarify in specification that, in absence of $format or accept header, service is allowed to return results in any format.

      The current olingo behavior is, unfortunately, correct given the headers specified by IE and Chrome.

      Show
      Clarify in specification that, in absence of $format or accept header, service is allowed to return results in any format. The current olingo behavior is, unfortunately, correct given the headers specified by IE and Chrome.
    • Resolution:
      Show
      https://www.oasis-open.org/committees/download.php/57136/odata-v4.0-wd08-part1-protocol-2015-12-15.docx

      Description

      As far as I could find, the spec does not define what the expected behavior should be when neither an accept header nor a $format query parameter is specified in a request. Does the server return the response in a spec defined default format or does the server get to choose which format to return results in.

      We should also cover the case of ambiguous Accept headers containing /: currently the Olingo server library responds to requests from IE and Chrome with Atom-XML:

      • Internet Explorer sends Accept: text/html, application/xhtml+xml, /
      • Chrome sends Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8
        As application/json isn't explicitly mentioned, they use application/xml

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mark.biamonte Mark Biamonte
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: