commit 06b19cd6f11396e11b95e5480e4b07897f3663e7
parent ace673ed30067aa50ef5eebe16cc63ebe1ae066d
Author: Christian Grothoff <grothoff@gnunet.org>
Date: Fri, 9 Feb 2024 15:48:45 +0100
start review of error messages
Diffstat:
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/gnu-taler-error-codes/registry.rec b/gnu-taler-error-codes/registry.rec
@@ -32,49 +32,49 @@ HttpStatus: 0
# We could not get the error code.
Value: 1
Name: INVALID
-Description: A non-integer error code was returned in the JSON response.
+Description: An error response did not include an error code in the format expected by the client. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
HttpStatus: 0
Value: 2
Name: GENERIC_CLIENT_INTERNAL_ERROR
-Description: An internal failure happened on the client side.
+Description: An internal failure happened on the client side. Details should be in the local logs. Check if you are using the latest available version or file a report with the developers.
HttpStatus: 0
# Fundamental problems detected client-side (10-19)
Value: 10
Name: GENERIC_INVALID_RESPONSE
-Description: The response we got from the server was not even in JSON format.
+Description: The response we got from the server was not in the expected format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
HttpStatus: 0
Value: 11
Name: GENERIC_TIMEOUT
-Description: An operation timed out.
+Description: The operation timed out. Trying again might help. Check the network connection.
HttpStatus: 0
Value: 12
Name: GENERIC_VERSION_MALFORMED
-Description: The version string given does not follow the expected CURRENT:REVISION:AGE Format.
+Description: The protocol version given by the server does not follow the required format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
HttpStatus: 0
Value: 13
Name: GENERIC_REPLY_MALFORMED
-Description: The service responded with a reply that was in JSON but did not satsify the protocol. Note that invalid cryptographic signatures should have signature-specific error codes.
+Description: The service responded with a reply that was in the right data format, but the content did not satisfy the protocol. Please file a bug report.
HttpStatus: 0
Value: 14
Name: GENERIC_CONFIGURATION_INVALID
-Description: There is an error in the client-side configuration, for example the base URL specified is malformed.
+Description: There is an error in the client-side configuration, for example an option is set to an invalid value. Check the logs and fix the local configuration.
HttpStatus: 0
Value: 15
Name: GENERIC_UNEXPECTED_REQUEST_ERROR
-Description: The client made a request to a service, but received an error response it does not know how to handle.
+Description: The client made a request to a service, but received an error response it does not know how to handle. Please file a bug report.
HttpStatus: 0
Value: 16
Name: GENERIC_TOKEN_PERMISSION_INSUFFICIENT
-Description: The token used by the client to authorize the request does not grant the required permissions for the request.
+Description: The token used by the client to authorize the request does not grant the required permissions for the request. Check the requirements and obtain a suitable authorization token to proceed.
HttpStatus: 403
# Fundamental client-side protocol problems (20-29)
@@ -82,27 +82,27 @@ HttpStatus: 403
Value: 20
Name: GENERIC_METHOD_INVALID
-Description: The HTTP method used is invalid for this endpoint.
+Description: The HTTP method used is invalid for this endpoint. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 405
Value: 21
Name: GENERIC_ENDPOINT_UNKNOWN
-Description: There is no endpoint defined for the URL provided by the client.
+Description: There is no endpoint defined for the URL provided by the client. Check if you used the correct URL and/or file a report with the developers of the client software.
HttpStatus: 404
Value: 22
Name: GENERIC_JSON_INVALID
-Description: The JSON in the client's request was malformed (generic parse error).
+Description: The JSON in the client's request was malformed. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 400
Value: 23
Name: GENERIC_HTTP_HEADERS_MALFORMED
-Description: Some of the HTTP headers provided by the client caused the server to not be able to handle the request.
+Description: Some of the HTTP headers provided by the client were malformed and caused the server to not be able to handle the request. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 400
Value: 24
Name: GENERIC_PAYTO_URI_MALFORMED
-Description: The payto:// URI provided by the client is malformed.
+Description: The payto:// URI provided by the client is malformed.
HttpStatus: 400
Value: 25
