On Wed, Sep 17, 2025 at 10:59 AM William Crowell <[email protected]> wrote: > > Hi, I asked the same question back in April, and here was the combined > response I got from Mark Thomas, Chris Schultz, and Rémy Maucherat: > > https://lists.apache.org/thread/l4f9f47hzytr28wvgw1fvl2k2gnplx4j > > “The QUIC plans have been on and off. Currently more off than on. If we were > to implement today, it would probably be with panama and a native QUIC stack. > > HTTP/3 runs over QUIC. It is a bit of a simplification but QUIC (and > therefore HTTP/3) essentially trades increased CPU usage at the client/server > for better tolerance of poor networks. > > Tomcat is not normally directly internet facing. It is typically sat behind > some form of load-balancer and/or TLS termination and/or reverse proxy. In > those scenarios poor network conditions aren't an issue so using QUIC is > costs CPU power which is something folks - particularly those with large > installations - try to minimize. It makes more sense to use HTTP/1.1 in those > scenarios. > > Hence there isn't much requirement for an HTTP/3 implementation in Tomcat at > the moment.”
Overall, it's doable, there are some examples in the OpenSSL code that would most likely work if adapted using FFM. The problem is that it makes an unreasonably large portion of the Tomcat runtime non JVM native code, which is probably not acceptable anymore. Rémy > Regards, > > William Crowell > > From: Jee仔 <[email protected]> > Date: Wednesday, September 17, 2025 at 4:45 AM > To: users <[email protected]> > Subject: HTTP/3 (QUIC) support > [You don't often get email from [email protected]. Learn why this is > important at https://aka.ms/LearnAboutSenderIdentification ] > > Dear Apache Tomcat Team, > I hope this message finds you well. I'm currently exploring HTTP/3 > integration possibilities and noticed that Tomcat doesn't yet natively > support this protocol. Could you kindly share if there are any plans to > implement HTTP/3 (QUIC) support in future releases? If so, would you mind > providing an estimated timeline? > Thank you for your time and consideration. > Best regards > > > Jee仔 > [email protected] > > > > > > > CAUTION: This email originated from outside of the organization. Do not click > on links or open attachments unless you recognize the sender and know the > content is safe. > > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
