Next in thread → Next in month →

[OASIS Issue Tracker] (ODATA-949) Clarify the effect Accept-Language header has on a delta response

From
OASIS Issues Tracker <>
Date
2016-07-28T16:58:09+00:00
ID
Thread
[OASIS Issue Tracker] (ODATA-949) Clarify the effect Accept-Language header has on a delta response
[ https://issues.oasis-open.org/browse/ODATA-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-949:
--------------------------------

    Proposal: 
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.

  was:The Accept-Language header should be ignored for delta responses.  The Accept-Language is treated similarly to a $filter and would be encoded in the delta link.


> Clarify the effect Accept-Language header has on a delta response
> -----------------------------------------------------------------
>
>                 Key: ODATA-949
>                 URL: https://issues.oasis-open.org/browse/ODATA-949
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>            Reporter: Matthew Borges
>            Priority: Minor
>             Fix For: V4.01_WD01, V4.0_ERRATA04
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →