diff options
author | Christian Grothoff <christian@grothoff.org> | 2021-09-01 18:13:39 +0200 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2021-09-01 18:13:39 +0200 |
commit | 5f95f26a257cce0fa2b9eac275dc31957fb68b29 (patch) | |
tree | 2c6576f402637f6774926871cf42d7bdf7930359 | |
parent | 13deb5c4d23a3e2151490d98bf711d0ad0e47007 (diff) | |
download | exchange-5f95f26a257cce0fa2b9eac275dc31957fb68b29.tar.gz exchange-5f95f26a257cce0fa2b9eac275dc31957fb68b29.zip |
suspend if /keys is not ready
-rw-r--r-- | src/exchange/taler-exchange-httpd_keys.c | 12 |
1 files changed, 3 insertions, 9 deletions
diff --git a/src/exchange/taler-exchange-httpd_keys.c b/src/exchange/taler-exchange-httpd_keys.c index d301c5def..6d062866e 100644 --- a/src/exchange/taler-exchange-httpd_keys.c +++ b/src/exchange/taler-exchange-httpd_keys.c | |||
@@ -2125,15 +2125,9 @@ TEH_keys_get_handler (struct TEH_RequestContext *rc, | |||
2125 | } | 2125 | } |
2126 | if (NULL == krd) | 2126 | if (NULL == krd) |
2127 | { | 2127 | { |
2128 | /* Maybe client picked time stamp too far in the future? In that case, | 2128 | /* Likely keys not ready *yet*. |
2129 | "INTERNAL_SERVER_ERROR" might be misleading, could be more like a | 2129 | Wait until they are. */ |
2130 | NOT_FOUND situation. But, OTOH, for 'sane' clients it is more likely | 2130 | return suspend_request (rc->connection); |
2131 | to be our fault, so let's speculatively assume we are to blame ;-) */// | ||
2132 | GNUNET_break (0); | ||
2133 | return TALER_MHD_reply_with_error (rc->connection, | ||
2134 | MHD_HTTP_INTERNAL_SERVER_ERROR, | ||
2135 | TALER_EC_EXCHANGE_GENERIC_KEYS_MISSING, | ||
2136 | "no key data for given timestamp"); | ||
2137 | } | 2131 | } |
2138 | return MHD_queue_response (rc->connection, | 2132 | return MHD_queue_response (rc->connection, |
2139 | MHD_HTTP_OK, | 2133 | MHD_HTTP_OK, |