View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010261 | Taler | wallet-core | public | 2025-08-19 13:41 | 2026-09-19 14:40 |
| Reporter | Christian Grothoff | 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 | major | Reproducibility | always |
| Status | informing | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | 1.0 | ||||
| Target Version | 1.6 | Fixed in Version | 1.6 | ||
| Summary | 0010261: wallet(-core) keeps requesting order status from merchant backend after 404 [4h] | ||||
| Description | I have a very old transaction that is rendered as "Transaction failed" in my (WebExtension) taler wallet. I noticed that the webextension makes GET requests to the backend (even if I don't view the transaction details) for each of these failed / old / ancient transactions, even though they have long expired and the merchant has deleted the orders. The merchant responds with a 404, but wallet-core keeps repeating the request. Once we grow, this will be deadly for merchant backends as they'll get DDoSed by Taler wallets requesting ancient orders. | ||||
| Tags | No tags attached. | ||||
| commit 3074e4580522201d8baad0f066fa12d4dbb079bb (HEAD -> master) Author: Florian Dold <dold@taler.net> Date: Wed Jul 29 12:47:01 2026 +0200 harness: check that a deleted order settles the payment transaction Issue: https://bugs.taler.net/n/10261 commit 17017a3d53155473433ac0f74a4939c063a43c48 Author: Florian Dold <dold@taler.net> Date: Wed Jul 29 12:46:57 2026 +0200 wallet-core: stop asking the merchant about a deleted order A merchant that deleted an order answers every request about it with the same 404, so the wallet's retries only piled up requests that could never be satisfied, for as long as the transaction existed. Issue: https://bugs.taler.net/n/10261 | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-08-19 13:41 | Christian Grothoff | New Issue | |
| 2025-08-19 13:41 | Christian Grothoff | Status | new => assigned |
| 2025-08-19 13:41 | Christian Grothoff | Assigned To | => Florian Dold |
| 2025-10-08 19:09 | Christian Grothoff | Target Version | 1.1 => 1.5 |
| 2026-02-16 11:41 | Florian Dold | Summary | wallet(-core) keeps requesting order status from merchant backend after 404 => wallet(-core) keeps requesting order status from merchant backend after 404 [4h] |
| 2026-02-22 13:32 | Christian Grothoff | Target Version | 1.5 => 1.6 |
| 2026-02-22 14:07 | Christian Grothoff | Status | assigned => implementing |
| 2026-05-29 19:09 | Christian Grothoff | Target Version | 1.6 => 1.8 |
| 2026-07-29 10:52 | Florian Dold | Status | implementing => informing |
| 2026-07-29 10:52 | Florian Dold | Resolution | open => fixed |
| 2026-07-29 10:52 | Florian Dold | Note Added: 0029302 | |
| 2026-07-29 10:52 | Florian Dold | Target Version | 1.8 => 1.6 |
| 2026-09-19 14:40 | Christian Grothoff | Fixed in Version | => 1.6 |