[taler-docs] branch master updated: -change 406 to 400

[gnunet]

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 9df45adc -change 406 to 400
9df45adc is described below

commit 9df45adc3bb4a4e4f38a5e8ba44d6f00058bcdc4
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Thu Mar 7 13:03:48 2024 +0100

    -change 406 to 400
---
 core/api-merchant.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/core/api-merchant.rst b/core/api-merchant.rst
index a291d9cf..d21d8073 100644
--- a/core/api-merchant.rst
+++ b/core/api-merchant.rst
@@ -288,17 +288,17 @@ Making the payment
     Either the client request is malformed or some specific processing error
     happened that may be the fault of the client as detailed in the JSON body
     of the response.
+    This includes the case where the payment is insufficient (sum is below
+    the required total amount, for example because the wallet calculated the
+    fees wrong).
   :http:statuscode:`402 Payment required`:
     There used to be a sufficient payment, but due to refunds the amount 
effectively
     paid is no longer sufficient. (If the amount is generally insufficient, we
-    return "406 Not Acceptable", only if this is because of refunds we return 
402.)
+    return "400 Bad Request", only if this is because of refunds we return 
402.)
   :http:statuscode:`403 Forbidden`:
     One of the coin signatures was not valid.
   :http:statuscode:`404 Not found`:
     The merchant backend could not find the order or the instance and thus 
cannot process the payment.
-  :http:statuscode:`406 Not acceptable`:
-    The payment is insufficient (sum is below the required total amount).
-    TODO: Should probably change to a different status code in the future as 
406 is technically wrong.
   :http:statuscode:`408 Request timeout`:
     The backend took too long to process the request. Likely the merchant's 
connection
     to the exchange timed out. Try again.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.