View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010760 | Taler | exchange | public | 2025-12-10 22:31 | 2025-12-11 07:02 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
| Priority | high | Severity | major | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Target Version | 1.4 | ||||
| Summary | 0010760: exchange treats AML rule names case-sensitively, causing subtle differences between tests and prod | ||||
| Description | The Taler configuration has case-insensitive section and option names. This means that tools that process the configuration may change the casing of sections/options. However, the exchange reports rule names (to AML programs and in the HTTP API) without normalizing the case. Some existing AML programs specifically only work with lower-case rule names. Since the taler-harness upper-cases section names when writing configuration values, the behavior between prod and the test harness differs. IMO this is not a bug in the harness but in the exchange. Changing the case of section names shall not effect the semantics. | ||||
| Tags | No tags attached. | ||||
|
|
@Christian: I can lower-case the rules from the config myself. But what what we should discuss: How are rules from the API treated? Are they also lower-cased? Do we treat it as an error if they're not lower-case? |
|
|
Exchange should normalize everything (OK with to lower-case). We didn't specify in the API, so best is to always normalize. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-12-10 22:31 | Florian Dold | New Issue | |
| 2025-12-10 22:50 | Florian Dold | Note Added: 0026868 | |
| 2025-12-11 07:00 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-12-11 07:00 | Christian Grothoff | Status | new => assigned |
| 2025-12-11 07:02 | Christian Grothoff | Note Added: 0026869 |
