bryancall commented on issue #11781: URL: https://github.com/apache/trafficserver/issues/11781#issuecomment-4828155852
Thanks for the suggestion. Building HTTP/3 against the OpenSSL/quictls fork (openssl-quic1) is already supported today: you build quiche with its openssl feature instead of BoringSSL, and Apache Traffic Server will use it. The build script does exactly this, see [tools/build_openssl_h3_tools.sh](https://github.com/apache/trafficserver/blob/master/tools/build_openssl_h3_tools.sh#L131), where quiche is built with the openssl feature flag.\n\nWorth clarifying the deeper question too: the OpenSSL fork only provides the Transport Layer Security primitives QUIC needs, not a QUIC implementation. Apache Traffic Server 9.2.x had our own QUIC implementation that used that fork, but we dropped it in 10.0 and switched to quiche because we do not have the resources to maintain a homegrown QUIC stack. So the path forward is quiche, and it can be built against OpenSSL/quictls as shown above.\n\nSince the OpenSSL-backed build already works and the native-implementation direction was a deliberate maintenance decision, I am closing this. Please reopen if you hit a specific problem building quiche against OpenSSL. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
