HTTP/3 extended CONNECT is not normalised to H1 format
Open
area/quic
bug
no stalebot
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 430
Description
*Title*: *HTTP/3 extended CONNECT is not normalised to H1 format*
*Description*:
>As part of our CONNECT-UDP implementation for envoy, we found that presently, HTTP/3 Extended Connect requests stay in HTTP/3 format, and this is a bug because they are therefore not recognized in any of the HTTP Upgrade routing logic. Therefore, we must normalise H3 requests, in a similar way to how we normalise HTTP/2 requests
Contributor guide
Assessment
This issue has not been assessed yet.