[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-861) Define behavior when neither accept header or $format query parameter is specified
[ https://issues.oasis-open.org/browse/ODATA-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-861: ----------------------------- Environment: Applied Component/s: (was: OData URL Conventions) > Define behavior when neither accept header or $format query parameter is specified > ---------------------------------------------------------------------------------- > > Key: ODATA-861 > URL: https://issues.oasis-open.org/browse/ODATA-861 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Sub-task > Components: OData Protocol > Affects Versions: V4.0_ERRATA02 > Environment: Applied > Reporter: Mark Biamonte > Priority: Minor > Fix For: V4.0_ERRATA03 > > > 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 -- 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]