2024-12-13 04:49 UTC

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002640NetSurfCore-specificpublic2024-05-24 20:00
ReporterFelix S. 
Assigned Tokinnison 
SeverityminorReproducibilityalways 
StatusclosedResolutionfixed 
PlatformGTK, FramebufferOSLinuxOS Version
Product Version3.8 
Target VersionFixed in Version3.11 
Summary0002640: Cannot browse Twitter
DescriptionAttempting to any page on the twitter.com domain generates a message: 'Error in the HTTP2 framing layer'. Opening mobile.twitter.com instead works fine.
TagsNo tags attached.
Fixed in CI build #
Reported in CI build #
URL of problem page
Attached Files

-Relationships
related to 0002634acknowledgedVincent Sanders crash in fetch_curl_poll 
+Relationships

-Notes
Vincent Sanders

~0001907

Vincent Sanders (administrator)

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.

~0001913

Felix S. (reporter)

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

~0001950

kinnison (administrator)

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

~0002090

kinnison (administrator)

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

~0002445

kinnison (administrator)

We updated cURL to include the fix.
+Notes

-Issue History
Date Modified Username Field Change
2019-04-07 10:08 Felix S. New Issue
2019-05-06 14:50 Vincent Sanders Status new => feedback
2019-05-06 14:50 Vincent Sanders Note Added: 0001907
2019-05-06 14:57 Vincent Sanders Relationship added related to 0002634
2019-05-10 15:23 Felix S. Note Added: 0001913
2019-05-10 15:23 Felix S. Status feedback => new
2019-06-09 15:04 kinnison Note Added: 0001950
2019-06-13 09:20 Vincent Sanders Status new => feedback
2019-09-08 07:42 kinnison Assigned To => kinnison
2019-09-08 07:42 kinnison Severity major => minor
2019-09-08 07:42 kinnison Status feedback => acknowledged
2019-09-08 07:42 kinnison Note Added: 0002090
2024-05-24 20:00 kinnison Status acknowledged => closed
2024-05-24 20:00 kinnison Resolution open => fixed
2024-05-24 20:00 kinnison Fixed in Version => 3.11
2024-05-24 20:00 kinnison Note Added: 0002445
+Issue History