[OASIS Issue Tracker] (ODATA-670) Clarify behavior wrt If-Match header on a GET request

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://tools.oasis-open.org/issues/browse/ODATA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-670:
--------------------------------

    Environment: [Applied]  (was: [Proposed])

> Clarify behavior wrt If-Match header on a GET request
> -----------------------------------------------------
>
>                 Key: ODATA-670
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-670
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol 
>    Affects Versions: V4.0_OS
>         Environment: [Applied]
>            Reporter: Hubert Heijkers
>            Assignee: Michael Pizzo
>            Priority: Minor
>             Fix For: V4.0_ERRATA01
>
>
> Section 9.1.6 of protocol incorrectly implies that a request containing an If-Match header should return a 304 Not Modified in the case the ETag specified in the If-Match header matches, which is incorrect.
> Clarify that if the If-Match header is used on a GET request and the content has changed that the server MUST return a 412 Precondition Failed and otherwise process the request as normal.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)