From c89231b29b7cf86a1c2a7eb5d730d122d1b55c14 Mon Sep 17 00:00:00 2001 From: Kjetil Kjernsmo Date: Mon, 2 Aug 2021 23:28:22 +0200 Subject: [PATCH 1/2] Put the If-None-Match: * requirement on the server --- protocol.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/protocol.html b/protocol.html index 9e7049f5..3a2f4acd 100644 --- a/protocol.html +++ b/protocol.html @@ -637,7 +637,7 @@

Writing Resources

Servers MUST NOT allow HTTP POST, PUT and PATCH to update a container’s containment triples; if the server receives such a request, it MUST respond with a 409 status code. [Source]

-

Clients MAY use the HTTP If-None-Match header with a value of "*" to prevent an unsafe request method (e.g., PUT, PATCH) from inadvertently modifying an existing representation of the target resource when the client believes that the resource does not have a current representation. [Source] [Source]

+

Servers MUST ensure that HTTP If-None-Match header with a value of "*" will prevent an unsafe request method (e.g., PUT, PATCH) from modifying an existing representation of the target resource. A client MAY use this header if it believes that the resource does not have a current representation. [Source] [Source]

Servers MAY use the HTTP ETag header with a strong validator for RDF bearing representations in order to encourage clients to opt-in to using the If-Match header in their requests.

From a8b625f3a4ef6dab50269c794c1bc03f01ed5669 Mon Sep 17 00:00:00 2001 From: Kjetil Kjernsmo Date: Tue, 3 Aug 2021 11:28:59 +0200 Subject: [PATCH 2/2] Update protocol.html Co-authored-by: Sarven Capadisli --- protocol.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/protocol.html b/protocol.html index 3a2f4acd..2ce82e8a 100644 --- a/protocol.html +++ b/protocol.html @@ -637,7 +637,7 @@

Writing Resources

Servers MUST NOT allow HTTP POST, PUT and PATCH to update a container’s containment triples; if the server receives such a request, it MUST respond with a 409 status code. [Source]

-

Servers MUST ensure that HTTP If-None-Match header with a value of "*" will prevent an unsafe request method (e.g., PUT, PATCH) from modifying an existing representation of the target resource. A client MAY use this header if it believes that the resource does not have a current representation. [Source] [Source]

+

Note:Clients are encouraged to use the HTTP If-None-Match header with a value of "*" to prevent an unsafe request method (e.g., PUT, PATCH) from inadvertently modifying an existing representation of the target resource when the client believes that the resource does not have a current representation. [Source] [Source] [Source]

Servers MAY use the HTTP ETag header with a strong validator for RDF bearing representations in order to encourage clients to opt-in to using the If-Match header in their requests.