8.2.5 If-None-Match: clarify use of If-None-Match in data modification or action requests

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.0_WD01
    • Affects Version/s: V4.0_WD01
    • Component/s: Protocol
    • None
    • Environment:

      [Proposed]

      Use of If-None-Match with GET is clear: conditionally refresh caches.

      Use of If-None-Match:* with PUT is to restrict the UPSERT behavior to true INSERT, for which OData already has POST ~/EntitySet, so this would just be an addition to ODATA-37.

      Use of If-None-Match with an ETag value is unclear: it seems to be just a performance-optimized version of "ignore what other people told you and do what I tell you now".

            Assignee:
            Unassigned
            Reporter:
            martinzurmuehl
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: