View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010096 | Taler | merchant portal webui | public | 2025-06-12 10:13 | 2025-08-31 17:10 |
| Reporter | Florian Dold | Assigned To | Florian Dold | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.0 stretch goals | Fixed in Version | 1.0 stretch goals | ||
| Summary | 0010096: merchant SPA should load /config with Cache-Control: no-cache when logged out | ||||
| Description | Otherwise changing settings in the merchant backend config won't take effect until the cache expires. Always fetching the configuration with caching disabled when currently not logged in is a good compromise, since it allows immediately applying config changes, but still minimizes network requests when logged in. Even force-reloading won't help here, as /config is fetched via JavaScript. | ||||
| Tags | No tags attached. | ||||
| I don't think this is a good solution since it will make all request to `/config` skip the cache. The SPA right know only does 1 query to /config on app start-up to make sure that the APP is working with a the right server version and saves the info on memory, there is no other request to /config. If the SPA is making more than one request to /config (without refresh), then is a app bug. I may be able to use `PerformanceNavigationTiming` to differentiate navigation between refresh this may be a overcomplication. why do we have here a server cache directive? /config is cheap and not too big, and from the SPA it should always be up-to-date. My suggestion is to drop the cache directive. For this an all the /config (exchange, challenger, bank) | |
| To add more, the size of index.js file is 2Mb and doesn't have a cache directive. The /config is only 1k The definitive solution will be to embed the /config response on the index.js file so the SPA doesn't have the need to do the request at all. And rename all the html resources (css, js, font) to have the hash of the content on the resource name so the browser only need to fetch the index.html ( less than 4kb ) to get the up-to-date app or load it from cache if nothing changed. | |
| The ceo says it `sounds reasonable` | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-12 10:13 | Florian Dold | New Issue | |
| 2025-06-12 10:29 | Christian Grothoff | Status | new => implementing |
| 2025-06-12 10:29 | Christian Grothoff | Target Version | 1.1 => 1.0 stretch goals |
| 2025-06-14 19:17 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-06-14 19:17 | Christian Grothoff | Status | implementing => assigned |
| 2025-06-16 12:30 | sebasjm | Note Added: 0025256 | |
| 2025-06-16 12:30 | sebasjm | Assigned To | sebasjm => Florian Dold |
| 2025-06-16 12:30 | sebasjm | Status | assigned => feedback |
| 2025-06-16 12:46 | sebasjm | Note Added: 0025257 | |
| 2025-06-16 20:15 | sebasjm | Status | feedback => informing |
| 2025-06-16 20:15 | sebasjm | Resolution | open => fixed |
| 2025-06-16 20:15 | sebasjm | Note Added: 0025260 | |
| 2025-08-31 17:09 | Christian Grothoff | Status | informing => closed |
| 2025-08-31 17:10 | Christian Grothoff | Fixed in Version | => 1.0 stretch goals |
| 2026-08-23 14:18 | Florian Dold | Category | merchant backoffice SPA => merchant portal webui |