summaryrefslogtreecommitdiff
path: root/src/lib/exchange_api_reserve.c
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2020-02-26 23:43:58 +0100
committerChristian Grothoff <christian@grothoff.org>2020-02-26 23:43:58 +0100
commit8062ca01361136a9d2489a2ca27b58802d37c228 (patch)
treee23c3f9ed7819832f8852ba9def2825b92f9ad69 /src/lib/exchange_api_reserve.c
parent502c9a0fc36bf8ee81e294827c7403519e174249 (diff)
downloadexchange-8062ca01361136a9d2489a2ca27b58802d37c228.tar.gz
exchange-8062ca01361136a9d2489a2ca27b58802d37c228.tar.bz2
exchange-8062ca01361136a9d2489a2ca27b58802d37c228.zip
proper generation of /refreshes/ requests
Diffstat (limited to 'src/lib/exchange_api_reserve.c')
-rw-r--r--src/lib/exchange_api_reserve.c13
1 files changed, 6 insertions, 7 deletions
diff --git a/src/lib/exchange_api_reserve.c b/src/lib/exchange_api_reserve.c
index 7fa3f308..c0dd66e8 100644
--- a/src/lib/exchange_api_reserve.c
+++ b/src/lib/exchange_api_reserve.c
@@ -783,11 +783,10 @@ struct TALER_EXCHANGE_ReserveWithdrawHandle
/**
- * We got a 200 OK response for the /reserve/withdraw operation.
- * Extract the coin's signature and return it to the caller.
- * The signature we get from the exchange is for the blinded value.
- * Thus, we first must unblind it and then should verify its
- * validity against our coin's hash.
+ * We got a 200 OK response for the /reserves/$RESERVE_PUB/withdraw operation.
+ * Extract the coin's signature and return it to the caller. The signature we
+ * get from the exchange is for the blinded value. Thus, we first must
+ * unblind it and then should verify its validity against our coin's hash.
*
* If everything checks out, we return the unblinded signature
* to the application via the callback.
@@ -843,7 +842,7 @@ reserve_withdraw_ok (struct TALER_EXCHANGE_ReserveWithdrawHandle *wsh,
/**
- * We got a 409 CONFLICT response for the /reserve/withdraw operation.
+ * We got a 409 CONFLICT response for the /reserves/$RESERVE_PUB/withdraw operation.
* Check the signatures on the withdraw transactions in the provided
* history and that the balances add up. We don't do anything directly
* with the information, as the JSON will be returned to the application.
@@ -955,7 +954,7 @@ reserve_withdraw_payment_required (struct
/**
* Function called when we're done processing the
- * HTTP /reserve/withdraw request.
+ * HTTP /reserves/$RESERVE_PUB/withdraw request.
*
* @param cls the `struct TALER_EXCHANGE_ReserveWithdrawHandle`
* @param response_code HTTP response code, 0 on error