[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: clarify docs
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: clarify docs |
Date: |
Mon, 14 Dec 2020 14:21:44 +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 48a21a1 clarify docs
new 9439aa9 Merge branch 'master' of git+ssh://git.taler.net/docs
48a21a1 is described below
commit 48a21a197665e9ef06a2fc8626f48de9038d46d1
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Mon Dec 14 14:21:37 2020 +0100
clarify docs
---
core/api-exchange.rst | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/core/api-exchange.rst b/core/api-exchange.rst
index a2b6e2a..9e4f24a 100644
--- a/core/api-exchange.rst
+++ b/core/api-exchange.rst
@@ -102,15 +102,13 @@ possibly by using HTTPS.
**Request:**
:query last_issue_date: optional argument specifying the maximum value of
any of the "stamp_start" members of the denomination keys of a "/keys" response
that is already known to the client. Allows the exchange to only return keys
that have changed since that timestamp. The given value must be an unsigned
64-bit integer representing seconds after 1970. If the timestamp does not
exactly match the "stamp_start" of one of the denomination keys, all keys are
returned.
- :query now: request that the exchange answer the request as if the current
time were the value given in "now". The given value must be an unsigned 64-bit
integer representing seconds after 1970. This option is used for testing, and
in production is likely not supported.
**Response:**
:http:statuscode:`200 OK`:
The exchange responds with a `ExchangeKeysResponse` object. This request
should
- virtually always be successful.
- :http:statuscode:`403 Forbidden`:
- The client specified the "now" argument, but the exchange does not allow
this option as per its configuration.
+ virtually always be successful. It only fails if the exchange is
misconfigured or
+ has not yet been provisioned with key signatures via
`taler-exchange-offline`.
**Details:**
--
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: clarify docs,
gnunet <=