FS#63924 - [curl] Enable HTTP3 Support

Attached to Project: Arch Linux
Opened by Sebastian Jug (jugs) - Thursday, 26 September 2019, 14:48 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 26 September 2019, 15:21 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

curl 7.66.0 supports experimental HTTP3 support: https://daniel.haxx.se/blog/2019/09/11/curl-7-66-0-the-parallel-http-3-future-is-here/
Build instructions: https://github.com/curl/curl/blob/master/docs/HTTP3.md#quiche-version


Additional info:
* curl 7.66.0


Steps to reproduce:
$ curl -I https://blog.cloudflare.com/ --http3
curl: (1) Unsupported protocol
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Thursday, 26 September 2019, 15:21 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Let's wait until http3, and the curl support for it, is ready for production.
Comment by Eli Schwartz (eschwartz) - Thursday, 26 September 2019, 15:20 GMT
Why would it make sense to ship experimental, unstable, off-by-default implementations of experimental, unstable IETF protocols that don't work anywhere except on demo servers?

We'd have to package an http3 implementation too, one of which relies on patched openssl versions and the other of which relies on a static copy of an openssl fork.

Upstream doesn't even recommend you enable http3 support in production.

Similar request in Debian, where the curl developer basically said "I don't think you should do this": https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940519#10

Loading...