diff options
Diffstat (limited to 'gnu-taler-error-codes/registry.rec')
-rw-r--r-- | gnu-taler-error-codes/registry.rec | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/gnu-taler-error-codes/registry.rec b/gnu-taler-error-codes/registry.rec index b76d973..1428077 100644 --- a/gnu-taler-error-codes/registry.rec +++ b/gnu-taler-error-codes/registry.rec | |||
@@ -32,49 +32,49 @@ HttpStatus: 0 | |||
32 | # We could not get the error code. | 32 | # We could not get the error code. |
33 | Value: 1 | 33 | Value: 1 |
34 | Name: INVALID | 34 | Name: INVALID |
35 | Description: A non-integer error code was returned in the JSON response. | 35 | 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. |
36 | HttpStatus: 0 | 36 | HttpStatus: 0 |
37 | 37 | ||
38 | Value: 2 | 38 | Value: 2 |
39 | Name: GENERIC_CLIENT_INTERNAL_ERROR | 39 | Name: GENERIC_CLIENT_INTERNAL_ERROR |
40 | Description: An internal failure happened on the client side. | 40 | 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. |
41 | HttpStatus: 0 | 41 | HttpStatus: 0 |
42 | 42 | ||
43 | # Fundamental problems detected client-side (10-19) | 43 | # Fundamental problems detected client-side (10-19) |
44 | 44 | ||
45 | Value: 10 | 45 | Value: 10 |
46 | Name: GENERIC_INVALID_RESPONSE | 46 | Name: GENERIC_INVALID_RESPONSE |
47 | Description: The response we got from the server was not even in JSON format. | 47 | 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. |
48 | HttpStatus: 0 | 48 | HttpStatus: 0 |
49 | 49 | ||
50 | Value: 11 | 50 | Value: 11 |
51 | Name: GENERIC_TIMEOUT | 51 | Name: GENERIC_TIMEOUT |
52 | Description: An operation timed out. | 52 | Description: The operation timed out. Trying again might help. Check the network connection. |
53 | HttpStatus: 0 | 53 | HttpStatus: 0 |
54 | 54 | ||
55 | Value: 12 | 55 | Value: 12 |
56 | Name: GENERIC_VERSION_MALFORMED | 56 | Name: GENERIC_VERSION_MALFORMED |
57 | Description: The version string given does not follow the expected CURRENT:REVISION:AGE Format. | 57 | 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. |
58 | HttpStatus: 0 | 58 | HttpStatus: 0 |
59 | 59 | ||
60 | Value: 13 | 60 | Value: 13 |
61 | Name: GENERIC_REPLY_MALFORMED | 61 | Name: GENERIC_REPLY_MALFORMED |
62 | 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. | 62 | 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. |
63 | HttpStatus: 0 | 63 | HttpStatus: 0 |
64 | 64 | ||
65 | Value: 14 | 65 | Value: 14 |
66 | Name: GENERIC_CONFIGURATION_INVALID | 66 | Name: GENERIC_CONFIGURATION_INVALID |
67 | Description: There is an error in the client-side configuration, for example the base URL specified is malformed. | 67 | 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. |
68 | HttpStatus: 0 | 68 | HttpStatus: 0 |
69 | 69 | ||
70 | Value: 15 | 70 | Value: 15 |
71 | Name: GENERIC_UNEXPECTED_REQUEST_ERROR | 71 | Name: GENERIC_UNEXPECTED_REQUEST_ERROR |
72 | Description: The client made a request to a service, but received an error response it does not know how to handle. | 72 | 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. |
73 | HttpStatus: 0 | 73 | HttpStatus: 0 |
74 | 74 | ||
75 | Value: 16 | 75 | Value: 16 |
76 | Name: GENERIC_TOKEN_PERMISSION_INSUFFICIENT | 76 | Name: GENERIC_TOKEN_PERMISSION_INSUFFICIENT |
77 | Description: The token used by the client to authorize the request does not grant the required permissions for the request. | 77 | 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. |
78 | HttpStatus: 403 | 78 | HttpStatus: 403 |
79 | 79 | ||
80 | # Fundamental client-side protocol problems (20-29) | 80 | # Fundamental client-side protocol problems (20-29) |
@@ -82,27 +82,27 @@ HttpStatus: 403 | |||
82 | 82 | ||
83 | Value: 20 | 83 | Value: 20 |
84 | Name: GENERIC_METHOD_INVALID | 84 | Name: GENERIC_METHOD_INVALID |
85 | Description: The HTTP method used is invalid for this endpoint. | 85 | 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. |
86 | HttpStatus: 405 | 86 | HttpStatus: 405 |
87 | 87 | ||
88 | Value: 21 | 88 | Value: 21 |
89 | Name: GENERIC_ENDPOINT_UNKNOWN | 89 | Name: GENERIC_ENDPOINT_UNKNOWN |
90 | Description: There is no endpoint defined for the URL provided by the client. | 90 | 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. |
91 | HttpStatus: 404 | 91 | HttpStatus: 404 |
92 | 92 | ||
93 | Value: 22 | 93 | Value: 22 |
94 | Name: GENERIC_JSON_INVALID | 94 | Name: GENERIC_JSON_INVALID |
95 | Description: The JSON in the client's request was malformed (generic parse error). | 95 | 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. |
96 | HttpStatus: 400 | 96 | HttpStatus: 400 |
97 | 97 | ||
98 | Value: 23 | 98 | Value: 23 |
99 | Name: GENERIC_HTTP_HEADERS_MALFORMED | 99 | Name: GENERIC_HTTP_HEADERS_MALFORMED |
100 | Description: Some of the HTTP headers provided by the client caused the server to not be able to handle the request. | 100 | 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. |
101 | HttpStatus: 400 | 101 | HttpStatus: 400 |
102 | 102 | ||
103 | Value: 24 | 103 | Value: 24 |
104 | Name: GENERIC_PAYTO_URI_MALFORMED | 104 | Name: GENERIC_PAYTO_URI_MALFORMED |
105 | Description: The payto:// URI provided by the client is malformed. | 105 | Description: The payto:// URI provided by the client is malformed. |
106 | HttpStatus: 400 | 106 | HttpStatus: 400 |
107 | 107 | ||
108 | Value: 25 | 108 | Value: 25 |