taler-docs

commit 9c48792a5c768c25aadd6a4d15e46e23fb88f039
parent 1c2b46d5a93d86dbc662c646f2453016aebf075b
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sat,  6 Feb 2021 17:59:21 +0100

update anastasis spec'

Diffstat:
M
anastasis.rst
 | 
15
++++-----------

1 file changed, 4 insertions(+), 11 deletions(-)
diff --git a/anastasis.rst b/anastasis.rst
@@ -533,11 +533,6 @@ In the following, UUID is always defined and used according to `RFC 4122`_.
      option will be checked before the ``304 Not modified``
      case.
 
-  *If-Match*: Unless the client expects to upload the first encrypted recovery document to this account, the client
-  SHOULD provide an Etag matching the latest version already known to the server.  If this
-  header is present, the server MUST refuse the upload if the latest known version prior to
-  this upload does not match the given Etag.
-
   *If-None-Match*: This header MUST be present and set to the SHA512 hash (Etag) of the body by the client.
   The client SHOULD also set the "Expect: 100-Continue" header and wait for "100 continue"
   before uploading the body.  The server MUST
@@ -566,8 +561,6 @@ In the following, UUID is always defined and used according to `RFC 4122`_.
     The response body MAY provide alternative means for payment.
   :http:statuscode:`403 Forbidden`:
     The required account signature was invalid.  The response body may elaborate on the error.
-  :http:statuscode:`409 Conflict`:
-    The *If-Match* Etag does not match the latest prior version known to the server.
   :http:statuscode:`413 Request entity too large`:
     The upload is too large *or* too small. The response body may elaborate on the error.
 
@@ -734,12 +727,12 @@ charge per truth operation using GNU Taler.
 
     }
 
-.. http:get:: /truth/$UUID[?response=$RESPONSE]
+.. http:get:: /truth/$UUID[?response=$H_RESPONSE]
 
-  Get the stored encrypted key share. If ``$RESPONSE`` is specified by the client, the server checks
-  if ``$RESPONSE`` matches the expected response specified before within the TruthUploadRequest_ (see encrypted_truth).
+  Get the stored encrypted key share. If ``$H_RESPONSE`` is specified by the client, the server checks
+  if ``$H_RESPONSE`` matches the expected response specified before within the TruthUploadRequest_ (see encrypted_truth).
   Also, the user has to provide the correct *truth_encryption_key* with every get request (see below).
-  When ``$RESPONSE`` is correct, the server responses with the encrypted key share.
+  When ``$H_RESPONSE`` is correct, the server responds with the encrypted key share.
   The encrypted key share is returned simply as a byte array and not in JSON format.
 
   **Response**: