View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008182 | Taler | deployment and operations | public | 2024-01-22 10:37 | 2024-03-07 20:49 |
Reporter | Christian Grothoff | Assigned To | javier.sepulveda | ||
Priority | normal | Severity | tweak | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
Product Version | git (master) | ||||
Target Version | 0.9.4 | Fixed in Version | 0.9.4 | ||
Summary | 0008182: long polling limited to 30s | ||||
Description | We use long polling in our APIs, and sometimes it makes sense for long polling to take many minutes. However, the nginx reverse proxy seems to be configured (possibly by default) to terminate HTTP requests after ~30s. We should significantly increase that timeout (say to 5 minutes) for all of our reverse proxies to Taler APIs (also on taler-ops). How to reproduce: see order1 in video-tutorials using timeout > 30s. Reported by Michael N. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2024-01-22 10:37 | Christian Grothoff | New Issue | |
2024-01-22 10:37 | Christian Grothoff | Status | new => assigned |
2024-01-22 10:37 | Christian Grothoff | Assigned To | => javier.sepulveda |
2024-01-23 12:19 | javier.sepulveda | Assigned To | javier.sepulveda => Christian Grothoff |
2024-01-23 20:14 | Christian Grothoff | Assigned To | Christian Grothoff => javier.sepulveda |
2024-01-23 20:15 | Christian Grothoff | Note Added: 0021004 | |
2024-01-24 11:36 | javier.sepulveda | Status | assigned => resolved |
2024-01-24 11:36 | javier.sepulveda | Resolution | open => fixed |
2024-01-24 11:36 | javier.sepulveda | Note Added: 0021017 | |
2024-01-25 22:30 | Christian Grothoff | Fixed in Version | => 0.9.4 |
2024-01-25 22:30 | Christian Grothoff | Target Version | 0.10 => 0.9.4 |
2024-03-07 20:49 | Christian Grothoff | Status | resolved => closed |