[taler-exchange] branch master updated: it is a POST, and information could change anytime, so caching isn't really a good idea

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository exchange.

The following commit(s) were added to refs/heads/master by this push:
     new bf9b7e16 it is a POST, and information could change anytime, so 
caching isn't really a good idea
bf9b7e16 is described below

commit bf9b7e168bfccb7a92793b50936ac404bdfb72d9
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Tue Jul 5 13:37:13 2022 +0200

    it is a POST, and information could change anytime, so caching isn't really 
a good idea
---
 src/exchange/taler-exchange-httpd_reserves_history.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/src/exchange/taler-exchange-httpd_reserves_history.c 
b/src/exchange/taler-exchange-httpd_reserves_history.c
index 2c936244..aa3f8ab5 100644
--- a/src/exchange/taler-exchange-httpd_reserves_history.c
+++ b/src/exchange/taler-exchange-httpd_reserves_history.c
@@ -96,8 +96,6 @@ reply_reserve_history_success (struct MHD_Connection 
*connection,
                                        MHD_HTTP_INTERNAL_SERVER_ERROR,
                                        
TALER_EC_GENERIC_JSON_ALLOCATION_FAILURE,
                                        NULL);
-  /* FIXME: should set explicit cache control headers
-     for this response to enable caching! */
   return TALER_MHD_REPLY_JSON_PACK (
     connection,
     MHD_HTTP_OK,

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