blob: 6a739ee4e4026267800e10a58234669b428c6be1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
# Exchange Wire Caching
## Issue Summary
When demoing Taler to an audience, sometimes withdrawing or other operations
fail. This can happen even with a fresh wallet.
## Root Cause
The browser caches the /keys and /wire response for a long time, even when the
wallet is re-installed.
Usually the cache expiration is set to when available denominations or signing
keys are expected to change. This can be a rather long time. We often have format changes
or re-deploys with different keys in-between.
## Remediation and Prevention
For demo and test, the exchange shall use shorter expiration times.
(https://bugs.gnunet.org/view.php?id=5747)
To force re-downloading of the exchange's information, we will implement
a client-version parameter to break the browser's cache.
(https://bugs.gnunet.org/view.php?id=5745)
## Discussion
|
