You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found that the current HTTP/3 in version 10.0 is implemented via Quiche. It might be possible to achieve this using openssl-quic1, which supports the BoringSSL API while being fully compatible with OpenSSL. This OpenSSL repository is maintained by Akamai and Microsoft, offering better support for QUIC and reducing the complexity of compiling HTTP/3 in ATS. Could the project team support this QUIC repository?
The text was updated successfully, but these errors were encountered:
Hi @pmkol , this is already possible. You can build quiche using openssl/quictls istead of borinssl and ATS will use it.
Have a look at this script which builds quiche with openssl support.
@pmkol Are you actually wondering if ATS can use the openssl fork to support QUIC without using Quiche? As you may know the openssl fork only provides functions that are required to implement QUIC. It does not provide QUIC implementation. ATS 9.2.x supported the openssl fork and we had own QUIC implementation, but we dropped it and switched to using Quiche on 10.0 because we don't have enough resource/time to maintain our own QUIC implementation.
I have found that the current HTTP/3 in version 10.0 is implemented via Quiche. It might be possible to achieve this using openssl-quic1, which supports the BoringSSL API while being fully compatible with OpenSSL. This OpenSSL repository is maintained by Akamai and Microsoft, offering better support for QUIC and reducing the complexity of compiling HTTP/3 in ATS. Could the project team support this QUIC repository?
The text was updated successfully, but these errors were encountered: