diff options
author | Christian Grothoff <christian@grothoff.org> | 2019-11-23 22:21:47 +0100 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2019-11-23 22:21:47 +0100 |
commit | 7aae6c90452c1e9bcae78a5e948f381c1165010a (patch) | |
tree | e4520eafe637260b87fabe9f272abd275a3b91d7 /src/lib/exchange_api_track_transfer.c | |
parent | 51e54bbaa18397f599e5078153671c98c719c695 (diff) | |
download | exchange-7aae6c90452c1e9bcae78a5e948f381c1165010a.tar.xz |
use CONFLICT for double spending to distinguish properly from FORBIDDEN for bad signatures
Diffstat (limited to 'src/lib/exchange_api_track_transfer.c')
-rw-r--r-- | src/lib/exchange_api_track_transfer.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib/exchange_api_track_transfer.c b/src/lib/exchange_api_track_transfer.c index 419998a2c..2c90bf199 100644 --- a/src/lib/exchange_api_track_transfer.c +++ b/src/lib/exchange_api_track_transfer.c @@ -279,7 +279,7 @@ handle_track_transfer_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_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 */ |