[OASIS Issue Tracker] (ODATA-1076) If-Match: align wording with RFC7232

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

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

Ralf Handl updated ODATA-1076:
------------------------------

        Summary: If-Match: align wording with RFC7232  (was: If-Match and If-None-Match: align wording with RFC7232)
    Environment: Optimistically applied
    Description: 
The section on If-Match explicitly requires "weak comparison" of ETags. 

This was in line with the then current draft of RFC7232, but the final version of RFC7232 requires strong comparison of ETag values for If-Match, see https://tools.ietf.org/html/rfc7232#section-3.1. 



  was:
The sections on If-Match and If-None-Match explicitly require "weak comparison" of ETags. 

This was in line with the then current draft of RFC7232, but the final version of RFC7232 requires strong comparison of ETag values, see https://tools.ietf.org/html/rfc7232#section-3.1. 

       Proposal: 
Point out that we intentionally deviate from RFC7232, and give reason:

If present, the request MUST only be processed if the specified ETag value matches the current ETag value of the target resource. Services sending ETag headers with weak ETags that only depend on the representation-independent entity state MUST use the weak comparison function because it is sufficient to prevent accidental overwrites. This is a deviation from [RFC7232]. 

  was:Do not mention comparison and just refer to RFC7232.


> If-Match: align wording with RFC7232
> ------------------------------------
>
>                 Key: ODATA-1076
>                 URL: https://issues.oasis-open.org/browse/ODATA-1076
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Protocol
>    Affects Versions: V4.01_CSD02
>         Environment: Optimistically applied
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.01_CSD02
>
>
> The section on If-Match explicitly requires "weak comparison" of ETags. 
> This was in line with the then current draft of RFC7232, but the final version of RFC7232 requires strong comparison of ETag values for If-Match, see https://tools.ietf.org/html/rfc7232#section-3.1. 



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