You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: spec/Rest-Binding/rest-update-resource.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,21 +49,21 @@ Partial Update (PATCH): A PATCH request to the linkset URI (e.g., with applicati
49
49
50
50
Because a resource's metadata can be modified by multiple actors, preventing concurrent overwrites is critical. To ensure data integrity, LWS servers and clients MUST implement optimistic concurrency control using conditional requests [[RFC 7232](https://datatracker.ietf.org/doc/html/rfc7232)] for all PUT and PATCH operations on a linkset resource.
51
51
52
-
Server Responsibilities:
52
+
Server Responsibilities:
53
53
54
-
A server MUST include an Etag header in its responses to GET and HEAD requests for a linkset resource.
54
+
A server MUST include an Etag header in its responses to GET and HEAD requests for a linkset resource.
55
55
56
-
Upon a successful PUT or PATCH on the linkset, the server MUST generate a new, unique Etag value for the modified linkset and return it in the Etag header of the response.
56
+
Upon a successful PUT or PATCH on the linkset, the server MUST generate a new, unique Etag value for the modified linkset and return it in the Etag header of the response.
57
57
58
-
Client Responsibilities:
58
+
Client Responsibilities:
59
59
60
-
When modifying a linkset resource, a client MUST include an If-Match header containing the most recent Etag it received for that resource.
60
+
When modifying a linkset resource, a client MUST include an If-Match header containing the most recent Etag it received for that resource.
61
61
62
-
Processing Rules:
62
+
Processing Rules:
63
63
64
-
If the If-Match header value does not match the linkset's current Etag, the server MUST reject the request with a 412 Precondition Failed status code.
64
+
If the If-Match header value does not match the linkset's current Etag, the server MUST reject the request with a 412 Precondition Failed status code.
65
65
66
-
If the If-Match header is missing from a PUT or PATCH request to a linkset URI, the server MUST reject the request with a 428 Precondition Required status code (RFC 6585).
66
+
If the If-Match header is missing from a PUT or PATCH request to a linkset URI, the server MUST reject the request with a 428 Precondition Required status code (RFC 6585).
0 commit comments