-
Notifications
You must be signed in to change notification settings - Fork 6
[Enhancement] Use the IETF draft-29 of HTTP/3 #16
Comments
Well the issue is that HTTP3 is not supported by crystal and not even HTTP2: crystal-lang/crystal#2125 (comment) |
No language has inbuilt support for HTTP/3 currently. There are only implementations currently as they're just drafts currently. However, this is going to change soon when the v1 draft RFC is released. It's also worth noting that lsquic and chromium are the only two network stacks with support for gquic |
The RFCs have been published |
This should be a one-line change from what I can see. Changing lsquic.cr/src/lsquic/client.cr Line 200 in cb01d0f
|
Was that even implemented in litespeed quic v2.18? |
Last time I checked, it was in the latest release a few months ago. So yes, it's likely there and hence why there's bindings for it. |
I wish it was that easy. But in order to do that, we need to upgrade lsquic, and upgrade the C bindings in lsquic.cr |
It didn't exist at the time of lsquic 2.18: https://github.com/litespeedtech/lsquic/tree/v2.18.1/src/liblsquic/client.cr#L200 |
Is your enhancement request related to a problem? Please describe.
Yes, lsquic causes a lot of signal 11 killed errors, so I thought this would be worth a shot to fix the issue
Describe the solution you'd like
Usage of the IETF draft instead of Google's draft
Describe alternatives you've considered
N/A
Additional context
Google Chrome uses the IETF drafts by default now
Relevant code at
lsquic.cr/src/lsquic/client.cr
Line 200 in cb01d0f
The text was updated successfully, but these errors were encountered: