+1 Dream * Excel * Explore * Inspire Jon McAlexander | Senior Infrastructure Engineer | Middleware/App Hosting | FHP | CTO | Wells Fargo Technology 8080 Cobblestone Rd | Urbandale, IA 50322 MAC: F4469-010 | +1 515 988 2508 | [email protected]<mailto:[email protected]>
Need to engage our teams? Click here: https://hop.cfapps.wellsfargo.net/mwae This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. From: William Crowell <[email protected]> Sent: Wednesday, September 17, 2025 3:59 AM To: Tomcat Users List <[email protected]> Subject: Re: HTTP/3 (QUIC) support My apologies I forgot to add: I think it would be better for now if HTTP/3 is required is to front Tomcat with NGINX as a reverse proxy. From: William Crowell <[email protected]<mailto:[email protected]>> Date: Wednesday, September 17, 2025 at 4:58 AM To: Tomcat Users List <[email protected]<mailto:[email protected]>> Subject: Re: HTTP/3 (QUIC) support 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://urldefense.com/v3/__https://lists.apache.org/thread/l4f9f47hzytr28wvgw1fvl2k2gnplx4j__;!!F9svGWnIaVPGSwU!ozwxodxoNDTqlqqk5hewOZxJBGVSvsK80Tm8tGMolNNpt26GR06ZmCSEr03b9-fYfWyWYoRD3qBD_lLi5esXtj-Byhrlih8BmA$<https://urldefense.com/v3/__https:/lists.apache.org/thread/l4f9f47hzytr28wvgw1fvl2k2gnplx4j__;!!F9svGWnIaVPGSwU!ozwxodxoNDTqlqqk5hewOZxJBGVSvsK80Tm8tGMolNNpt26GR06ZmCSEr03b9-fYfWyWYoRD3qBD_lLi5esXtj-Byhrlih8BmA$> “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.” Regards, William Crowell From: Jee仔 <[email protected]<mailto:[email protected]>> Date: Wednesday, September 17, 2025 at 4:45 AM To: users <[email protected]<mailto:[email protected]>> Subject: HTTP/3 (QUIC) support [You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important at https://urldefense.com/v3/__https://aka.ms/LearnAboutSenderIdentification__;!!F9svGWnIaVPGSwU!ozwxodxoNDTqlqqk5hewOZxJBGVSvsK80Tm8tGMolNNpt26GR06ZmCSEr03b9-fYfWyWYoRD3qBD_lLi5esXtj-ByhqqKrKUlg$<https://urldefense.com/v3/__https:/aka.ms/LearnAboutSenderIdentification__;!!F9svGWnIaVPGSwU!ozwxodxoNDTqlqqk5hewOZxJBGVSvsK80Tm8tGMolNNpt26GR06ZmCSEr03b9-fYfWyWYoRD3qBD_lLi5esXtj-ByhqqKrKUlg$> ] 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]<mailto:[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. 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.
