From 0ca3dea0bd9422011f440da79b32df189dcdf479 Mon Sep 17 00:00:00 2001 From: Hugh Nimmo-Smith Date: Tue, 23 Apr 2024 17:26:39 +0100 Subject: [PATCH] The If-Match header on PUT requests contains the ETag --- proposals/4108-oidc-qr-login.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/4108-oidc-qr-login.md b/proposals/4108-oidc-qr-login.md index da5d5356..ac85b678 100644 --- a/proposals/4108-oidc-qr-login.md +++ b/proposals/4108-oidc-qr-login.md @@ -50,9 +50,9 @@ In this way, Device A and Device B can communicate by repeatedly inspecting and #### The send mechanism -Every send request MUST include an `ETag` header, whose value is supplied by the `ETag` header in the last `GET` +Every send request MUST include an `If-Match` header whose value is the `ETag` header in the last `GET` response seen by the requester. (The initiating device may also use the `ETag` supplied in the initial `POST` response -to immediately update the payload.) Updates will succeed only if the supplied `ETag` matches the server's current +to immediately update the payload.) Sends will succeed only if the supplied `ETag` matches the server's current revision of the payload. This prevents concurrent writes to the payload. The `ETag` header is standard, described by [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-etag). In this