[taler-exchange] 07/12: proper generation of /refreshes/ requests

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository exchange.

commit 8062ca01361136a9d2489a2ca27b58802d37c228
Author: Christian Grothoff <address@hidden>
AuthorDate: Wed Feb 26 23:43:58 2020 +0100

    proper generation of /refreshes/ requests
---
 src/lib/exchange_api_refresh.c | 10 +++++-----
 src/lib/exchange_api_reserve.c | 13 ++++++-------
 2 files changed, 11 insertions(+), 12 deletions(-)

diff --git a/src/lib/exchange_api_refresh.c b/src/lib/exchange_api_refresh.c
index 7a1304c1..eb26b7c1 100644
--- a/src/lib/exchange_api_refresh.c
+++ b/src/lib/exchange_api_refresh.c
@@ -1290,11 +1290,11 @@ TALER_EXCHANGE_refresh_melt_cancel (struct
 }
 
 
-/* ********************* /refresh/reveal ***************************** */
+/* ********************* /refreshes/$RCH/reveal ***************************** 
*/
 
 
 /**
- * @brief A /refresh/reveal Handle
+ * @brief A /refreshes/$RCH/reveal Handle
  */
 struct TALER_EXCHANGE_RefreshRevealHandle
 {
@@ -1344,7 +1344,7 @@ struct TALER_EXCHANGE_RefreshRevealHandle
 
 
 /**
- * We got a 200 OK response for the /refresh/reveal operation.
+ * We got a 200 OK response for the /refreshes/$RCH/reveal operation.
  * Extract the coin signatures and return them to the caller.
  * The signatures we get from the exchange is for the blinded value.
  * Thus, we first must unblind them and then should verify their
@@ -1449,7 +1449,7 @@ refresh_reveal_ok (struct 
TALER_EXCHANGE_RefreshRevealHandle *rrh,
 
 /**
  * Function called when we're done processing the
- * HTTP /refresh/reveal request.
+ * HTTP /refreshes/$RCH/reveal request.
  *
  * @param cls the `struct TALER_EXCHANGE_RefreshHandle`
  * @param response_code HTTP response code, 0 on error
@@ -1718,7 +1718,7 @@ TALER_EXCHANGE_refresh_reveal (struct 
TALER_EXCHANGE_Handle *exchange,
   rrh->reveal_cb_cls = reveal_cb_cls;
   rrh->md = md;
   rrh->url = TEAH_path_to_url (rrh->exchange,
-                               "/refresh/reveal");
+                               arg_str);
 
   eh = TEL_curl_easy_get (rrh->url);
   if (GNUNET_OK !=
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

-- 
To stop receiving notification emails like this one, please contact
address@hidden.