View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009552 | Taler | challenger | public | 2025-02-17 08:35 | 2025-05-10 02:11 |
| Reporter | Christian Grothoff | Assigned To | sebasjm | 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 | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.0 | Fixed in Version | 1.0 | ||
| Summary | 0009552: challenger SPA refuses to load without restrictions | ||||
| Description | I get "invalid server configuration, there is no restriction in /config". The message is correct in that 'restrictions: {}' in /config. But who says that there MUST be restrictions? While unusual, it is certainly conceivable that there simply are no restrictions. The challenger-httpd is perfectly happy to launch with an empty set, and thus so should the SPA! | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-02-17 08:35 | Christian Grothoff | New Issue | |
| 2025-02-17 08:35 | Christian Grothoff | Status | new => assigned |
| 2025-02-17 08:35 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-03-11 19:18 | sebasjm | Note Added: 0024178 | |
| 2025-03-11 19:18 | sebasjm | Status | assigned => informing |
| 2025-03-11 19:18 | sebasjm | Resolution | open => fixed |
| 2025-03-21 01:07 | Christian Grothoff | Fixed in Version | => 1.0 |
| 2025-03-21 01:07 | Christian Grothoff | Target Version | 1.0 stretch goals => 1.0 |
| 2025-05-10 02:11 | Christian Grothoff | Status | informing => closed |