OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-1096) 9.1.4 Response Code 204 No Content: rephrase second paragraph


Ralf Handl created ODATA-1096:
---------------------------------

             Summary: 9.1.4 Response Code 204 No Content: rephrase second paragraph
                 Key: ODATA-1096
                 URL: https://issues.oasis-open.org/browse/ODATA-1096
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: Protocol
    Affects Versions: V4.01_CSD02
            Reporter: Ralf Handl
             Fix For: V4.01_CS01


The second paragraph of section 9.1.4 is a quote from RFC7231 and somewhat hard to parse. Replace it with text that expresses its intention: send an ETag only if the client can reasonably "know" the current entity representation that has not been sent in the response:

(1) For a PUT request: if the response body of a corresponding 200 response would have been identical to the request body, i.e. no server-side modification of values sent in the request body, no "calculated" values. 

(2) We could extend this to PATCH requests and if a corresponding 200 response would have consisted of
- values sent in PATCH request body, plus 
- server-side values corresponding to ETag sent in If-Match header of PATCH request (for values not sent in PATCH request body)



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]