summaryrefslogtreecommitdiff
path: root/src/lib/exchange_api_deposit.c
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2019-11-23 22:21:47 +0100
committerChristian Grothoff <christian@grothoff.org>2019-11-23 22:21:47 +0100
commit7aae6c90452c1e9bcae78a5e948f381c1165010a (patch)
treee4520eafe637260b87fabe9f272abd275a3b91d7 /src/lib/exchange_api_deposit.c
parent51e54bbaa18397f599e5078153671c98c719c695 (diff)
downloadexchange-7aae6c90452c1e9bcae78a5e948f381c1165010a.tar.gz
exchange-7aae6c90452c1e9bcae78a5e948f381c1165010a.tar.bz2
exchange-7aae6c90452c1e9bcae78a5e948f381c1165010a.zip
use CONFLICT for double spending to distinguish properly from FORBIDDEN for bad signatures
Diffstat (limited to 'src/lib/exchange_api_deposit.c')
-rw-r--r--src/lib/exchange_api_deposit.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/lib/exchange_api_deposit.c b/src/lib/exchange_api_deposit.c
index 48f9a06b..30bb6c97 100644
--- a/src/lib/exchange_api_deposit.c
+++ b/src/lib/exchange_api_deposit.c
@@ -325,7 +325,7 @@ handle_deposit_finished (void *cls,
/* This should never happen, either us or the exchange is buggy
(or API version conflict); just pass JSON reply to the application */
break;
- case MHD_HTTP_FORBIDDEN:
+ case MHD_HTTP_CONFLICT:
/* Double spending; check signatures on transaction history */
if (GNUNET_OK !=
verify_deposit_signature_forbidden (dh,
@@ -335,7 +335,7 @@ handle_deposit_finished (void *cls,
response_code = 0;
}
break;
- case MHD_HTTP_UNAUTHORIZED:
+ case MHD_HTTP_FORBIDDEN:
/* Nothing really to verify, exchange says one of the signatures is
invalid; as we checked them, this should never happen, we
should pass the JSON reply to the application */