| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007851 | Taler | wallet (WebExtension) | public | 2023-05-31 13:33 | 2023-09-23 13:09 |
| Reporter | sebasjm | 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 | major | Reproducibility | sometimes |
| Status | closed | Resolution | won't fix | ||
| Product Version | git (master) | ||||
| Fixed in Version | 0.9.3 | ||||
| Summary | 0007851: we need a way to test that a new query does not break CORS requirement | ||||
| Description | I'm happy to take this but after we agree how we can do it and IF we can do it. The current situation: When wallet core queries /config of demobank it is adding the header ``` Access-Control-Request-Headers: 0 ``` in the OPTION request. Chrome is not doing the OPTION request. Firefox does it, and fails because the response of the server does not match with the request requirement. easy to fix, but hard to find. What I want with this issue is that we found a way to prevent this issue to happen, maybe with unit test or with a clear message error. Things to consider: * CORS request failure are opaque: usually seen as "request failed" * Depends on the platform: is it possible to simulate in node? * The error may also depend on the server response | ||||
| Tags | No tags attached. | ||||
- Anonymous