Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.01_CSD02
    • Fix Version/s: V4.01_CSD02
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      Optimistically applied

    • Proposal:
      Hide

      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].

      Show
      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] .
    • Resolution:
      Show
      https://www.oasis-open.org/committees/download.php/60942/odata-v4.01-wd02-part1-protocol-2017-06-07.docx

      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.

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              handl Ralf Handl
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: