Clarify the effect Accept-Language header has on a delta response

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • V4.01_WD01
    • Affects Version/s: None
    • Component/s: Protocol
    • None
    • Hide

      Revised proposal from 2016-7-28: Clients SHOULD specify the same Accept-Language header when querying the delta link as was specified in the defining query. Services MAY return Not Acceptable if a different Accept-Language is specified.

      If a service does support an Accept-Language header it MAY return changes only visible in that language, or MAY return records that have changes not visible in the requested language.

      Show
      Revised proposal from 2016-7-28: Clients SHOULD specify the same Accept-Language header when querying the delta link as was specified in the defining query. Services MAY return Not Acceptable if a different Accept-Language is specified. If a service does support an Accept-Language header it MAY return changes only visible in that language, or MAY return records that have changes not visible in the requested language.
    • Hide

      https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59028/odata-v4.01-wd01-part1-protocol.docx

      Show
      https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59028/odata-v4.01-wd01-part1-protocol.docx

      A client could issue a defining request with one value of the Accept-Language header and then use the returned delta link with a different Accept-Language. The spec isn't clear as to whether the delta response should ignore the Accept-Language or return unchanged entities but with the language dependent properties reflecting the newly specified language.

            Assignee:
            Unassigned
            Reporter:
            matt.borges
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: