[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: add timeout_ms arg to spec
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: add timeout_ms arg to spec |
Date: |
Sat, 13 Mar 2021 10:31:20 +0100 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new a40f6cb add timeout_ms arg to spec
a40f6cb is described below
commit a40f6cb9e921d1ae13203a502bafe8ca5cf636d3
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sat Mar 13 10:31:14 2021 +0100
add timeout_ms arg to spec
---
anastasis.rst | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/anastasis.rst b/anastasis.rst
index 61b0ed9..a427de9 100644
--- a/anastasis.rst
+++ b/anastasis.rst
@@ -529,6 +529,10 @@ In the following, UUID is always defined and used
according to `RFC 4122`_.
may attempt to upload the latest backup again, as this
option will be checked before the ``304 Not modified``
case.
+ :query timeout_ms=NUMBER: *Optional.* If specified, the Anastasis server
will
+ wait up to ``timeout_ms`` milliseconds for completion of the payment before
+ sending the HTTP response. A client must never rely on this behavior, as
the
+ backend may return a response immediately.
*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"
@@ -673,6 +677,15 @@ charge per truth operation using GNU Taler.
Upload a TruthUploadRequest_-Object according to the policy the client
created before (see RecoveryDocument_).
If request has been seen before, the server should do nothing, and otherwise
store the new object.
+ **Request:**
+
+ :query timeout_ms=NUMBER: *Optional.* If specified, the Anastasis server
will
+ wait up to ``timeout_ms`` milliseconds for completion of the payment before
+ sending the HTTP response. A client must never rely on this behavior, as
the
+ backend may return a response immediately.
+
+ **Response:**
+
:http:statuscode:`204 No content`:
Truth stored successfully.
:http:statuscode:`304 Not modified`:
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: add timeout_ms arg to spec,
gnunet <=