View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011058 | Taler | exchange | public | 2026-02-13 10:54 | 2026-03-20 23:55 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | 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 | high | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.5 | Fixed in Version | 1.5 | ||
| Summary | 0011058: exchange does not log taler error code on error responses | ||||
| Description | It only logs 0 even for error responses: Feb 13 11:42:19 spec taler-exchange-httpd[86209]: (444Q8B1VDGEQ082MFZP9E754ZM) WARNING External protocol violation detected at taler-exchange-httpd_reserves_purse.c:695. [...] Feb 13 11:42:19 spec taler-exchange-httpd[86209]: (444Q8B1VDGEQ082MFZP9E754ZM) INFO Request for `/reserves/<redacted>/purse' completed with HTTP status 400 (0) Clearly, the code for TALER_EC_EXCHANGE_RESERVES_PURSE_EXPIRATION_BEFORE_NOW should be logged, not zero. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-02-13 10:54 | Florian Dold | New Issue | |
| 2026-02-13 10:54 | Florian Dold | Status | new => assigned |
| 2026-02-13 10:54 | Florian Dold | Assigned To | => Christian Grothoff |
| 2026-02-14 21:40 | Christian Grothoff | Status | assigned => informing |
| 2026-02-14 21:40 | Christian Grothoff | Resolution | open => fixed |
| 2026-02-14 21:40 | Christian Grothoff | Fixed in Version | => 1.5 |
| 2026-03-20 23:55 | Christian Grothoff | Status | informing => closed |