|
Notes |
|
|
|
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 |
|
|
|
|
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. |
|
|
|
|
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. |
|
|
|
|
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 |
|
|
|
|
|
We updated cURL to include the fix. |
|