| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0002640 | NetSurf | Core-specific | public | 2019-04-07 11:08 | 2024-05-24 21:00 | ||||
| Reporter | Felix S. | ||||||||
| Assigned To | kinnison | ||||||||
| Severity | minor | Reproducibility | always | ||||||
| Status | closed | Resolution | fixed | ||||||
| Platform | GTK, Framebuffer | OS | Linux | OS Version | |||||
| Product Version | 3.8 | ||||||||
| Target Version | Fixed in Version | 3.11 | |||||||
| Summary | 0002640: Cannot browse Twitter | ||||||||
| Description | Attempting to any page on the twitter.com domain generates a message: 'Error in the HTTP2 framing layer'. Opening mobile.twitter.com instead works fine. | ||||||||
| Tags | No tags attached. | ||||||||
| Fixed in CI build # | |||||||||
| Reported in CI build # | |||||||||
| URL of problem page | |||||||||
| Attached Files |
| ||||||||
 Relationships |
||||||
|
||||||
 Relationships |
| Notes |
|
Vincent Sanders (administrator) 2019-05-06 15:50 |
It appears you have a libcurl that supports http2. We have not tested this configuration. Please can you provide more information on your platform (Linux distribution, version etc.) so we can attempt to reproduce |
Felix S. (reporter) 2019-05-10 16:23 |
Stock Debian buster/sid, the platform is i386. Currently using a git snapshot build based on NetSurf 3.8 (because Debian repos only contain 3.6...), built against libcurl4:i386 7.64.0-2; but I remember the issue appearing even in stock distro build, i.e. 3.6-3.2, which uses the same libcurl4 anyway. Why would HTTP2 make a difference, anyway? I'd have expected curl would have made it transparent. |
kinnison (administrator) 2019-06-09 16:04 |
While the expectation is that it ought to be transparent, it somehow does not appear to be so. Or at least it crashes for us. Could you please try with current master which disables http/2 for now. |
|
kinnison (administrator) 2019-09-08 08:42 |
It has been discovered that the issue lies within cURL itself. For now we're locking cURL to HTTP/1.1 and we'll look at reenabling HTTP/2 once there's a fixed libcurl. https://github.com/curl/curl/issues/4303 |
|
kinnison (administrator) 2024-05-24 21:00 |
We updated cURL to include the fix. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-04-07 11:08 | Felix S. | New Issue | |
| 2019-05-06 15:50 | Vincent Sanders | Status | new => feedback |
| 2019-05-06 15:50 | Vincent Sanders | Note Added: 0001907 | |
| 2019-05-06 15:57 | Vincent Sanders | Relationship added | related to 0002634 |
| 2019-05-10 16:23 | Felix S. | Note Added: 0001913 | |
| 2019-05-10 16:23 | Felix S. | Status | feedback => new |
| 2019-06-09 16:04 | kinnison | Note Added: 0001950 | |
| 2019-06-13 10:20 | Vincent Sanders | Status | new => feedback |
| 2019-09-08 08:42 | kinnison | Assigned To | => kinnison |
| 2019-09-08 08:42 | kinnison | Severity | major => minor |
| 2019-09-08 08:42 | kinnison | Status | feedback => acknowledged |
| 2019-09-08 08:42 | kinnison | Note Added: 0002090 | |
| 2024-05-24 21:00 | kinnison | Status | acknowledged => closed |
| 2024-05-24 21:00 | kinnison | Resolution | open => fixed |
| 2024-05-24 21:00 | kinnison | Fixed in Version | => 3.11 |
| 2024-05-24 21:00 | kinnison | Note Added: 0002445 | |
| Issue History |