View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009101 | Taler | exchange | public | 2024-08-20 14:26 | 2024-08-28 23:31 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 0.13 | Fixed in Version | 0.13 | ||
| Summary | 0009101: exchange measure names are case sensitive, but section names in the config are case-insensitive | ||||
| Description | When a measure (or program, check, ...) is specified in an option (e.g. "next_measures"), the exchange treats this name in a case-sensitive manner. The measure itself is defined in a section. According to the taler.conf documentation, the section name is **case insensitive**. However, the exchange treats the section name as case-sensitive for measures. That results in valid configurations breaking when the case of a section name is changed, which violates the spec of our config format. | ||||
| Tags | No tags attached. | ||||
|
|
Yes, sounds like we need to find some strcmp() and replace with strcasecmp(). |
|
|
b19627a1..1590a0aa replaces many strcmp() with strcasecmp(). This should include all cases relating to measure names. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-08-20 14:26 | Florian Dold | New Issue | |
| 2024-08-20 14:26 | Florian Dold | Status | new => assigned |
| 2024-08-20 14:26 | Florian Dold | Assigned To | => Christian Grothoff |
| 2024-08-22 14:43 | Christian Grothoff | Note Added: 0023031 | |
| 2024-08-22 17:50 | Christian Grothoff | Status | assigned => resolved |
| 2024-08-22 17:50 | Christian Grothoff | Resolution | open => fixed |
| 2024-08-22 17:50 | Christian Grothoff | Fixed in Version | => 0.13 |
| 2024-08-22 17:50 | Christian Grothoff | Note Added: 0023032 | |
| 2024-08-28 23:31 | Christian Grothoff | Status | resolved => closed |
