Clarify behavior wrt If-Match header on a GET request

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor
    • V4.0_ERRATA01
    • Affects Version/s: V4.0_OS
    • Component/s: Protocol
    • None
    • Environment:

      [Applied]

    • Hide

      See Description.

      Show
      See Description.

      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.

            Assignee:
            Michael Pizzo (Inactive)
            Reporter:
            Hubert Heijkers (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: