| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010733 | Taler | merchant backoffice SPA | public | 2025-12-05 11:08 | 2025-12-05 15:20 |
| Reporter | Christian Grothoff | Assigned To | sebasjm | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.5 | ||||
| Summary | 0010733: 451 response not handled by spa for template instantiation | ||||
| Description | When the SPA receives a 451 from POSTing a template, it fails with a "Reponse invalid" message instead of pointing the user to the KYC requirement. | ||||
| Steps To Reproduce | Start with fresh merchant backend. Run taler-merchant-dbinit, and start ONLY taler-merchant-httpd. Create an instance. Create a bank account. Create a template. Use the template with the "Test" button. Set the amount to be > 1. Kaboom. | ||||
| Additional Information | Here, the exchange interaction (taler-merchant-kyccheck, taler-merchant-exchangekeyupdate) were deliberately not running, so the operation failed because no exchange was available to handle the amount. Now, I used an existing DB (didn't fully reset the DB), so maybe some additional steps _could_ be needed to get here, but I think the above is enough and in any case, 451 handling is the issue. | ||||
| Tags | No tags attached. | ||||
|
|
the merchant spa has a handler for 451, invalid response means something else |
|
|
the problem is that PaymentDeniedLegallyResponse is expecting exchange_base_urls This can rendered on "developer mode" under personalization. I will use this issue to improve the message for the normal user I will also move out the developer mode of the personalization profile so you will be able to see this type of message to help debugging without moving out from the profile setting you are testing. image.png (65,243 bytes) |
|
|
now the codec will convert the missing exchange_base_urls into empty list for compatibility and this is how it looks image-2.png (65,312 bytes) |
