If-None-Match Missing / Presumed in LRS Concurrency Requirements
Morning team,
Reading through the concurrency changes to prep the 2.0 branch of the LRS CTS, it looks like the If-None-Match
header isn't explicitly mentioned in the LRS Requirements portion of the spec:
An LRS responding to a PUT, POST, or DELETE request shall handle the "If-Match" header as described in RFC2616, HTTP 1.1 in order to detect modifications made after the document was last fetched.
which makes it difficult to understand the use of "either" during a later sentence in that section:
If the header precondition in either of the request cases above fails, the LRS ...
The 1.0.3 spec document cleared this up for me by mentioning the If-None-Match
header must also be handled. For clarity, should this section also include that header, or are If-Match
and If-None-Match
just a known / presumed pairing?
Thanks,
-Trey