I've been reviewing your changes locally, tweaking them, and merging them on my end.
I don't ever rebase trunk without a good reason. What happened was I pushed a few thousand lines of code changes, then was immediately advised to revert them. I could have simply put the reversion on top of HEAD, but I didn't want HEAD~1 to show a +/- 3k line change followed by a +/- 6k revert and different approach on HEAD. A clean git history serves as good context for what changed and when. I removed ngtcp2 experimental support and updated the OpenSSL QUIC interface. On Thu, Aug 13, 2026, 6:19 AM Oleksandr Gerasymov via dev < [email protected]> wrote: > No, because machine-moon made additional changes and rebased the trunk > branch. Now my branch cannot be merged into it. Also none of my PRs are > accepted or even commented on now, so I am still working with my own > version. > > On Thu, Aug 13, 2026 at 11:51 AM jean-frederic clere <[email protected]> > wrote: > >> On 8/10/26 2:51 PM, Aleksandr Gerasimov via dev wrote: >> > Dear httpd developers, >> > >> > HTTP/3 support in httpd has been a long-awaited feature, and it is >> great >> > to see this work moving forward. >> > >> > I reviewed Machine Moon's mod_http3 implementation and have been >> > maintaining a fork with additional work aimed at making it practical >> for >> > existing httpd 2.4.x installations and bringing its behavior closer to >> > mod_http2, mod_ssl, and the httpd core. >> > >> > Among other things, I added stock httpd 2.4.52+ compatibility, mod_ssl- >> > compatible SSL_* environment variables, request header limit handling, >> > H3 stream timeouts and abuse limits, QPACK dynamic table support, >> > configurable worker limits, TLS session ticket and early-data controls, >> > and several QUIC I/O and lifecycle fixes. >> > >> > We have been building and testing it with httpd 2.4.68 and are very >> > happy with the results so far. >> > >> > I would also like to ask whether there is interest in bringing this >> > functionality to the official 2.4.x branch. There is a large installed >> > base on 2.4.x, and having HTTP/3 available there would make the feature >> > much more accessible without requiring users to wait for or immediately >> > migrate to the next major httpd release. >> > >> > If httpd PR #699 pull request against the 2.4.x branch would be useful, >> > I would be happy to prepare and submit one. >> > >> > My fork with the additional changes is here: >> > https://github.com/xl32/mod_http3 <https://github.com/xl32/mod_http3> >> >> The PR you did for https://github.com/machine-moon/mod_http3 are >> covering all your changes? >> >> > >> > Thank you for your work on httpd! >> > >> > >> > Best regards, >> > Oleksandr Gerasymov >> > CIO >> > CodeIT >> > CodeIT Logo >> > *W*: codeit.pro <https://codeit.pro> >> > >> > On 8/7/2026 5:05 PM, Steffen wrote: >> >> Good day, >> >> >> >> Developing an HTTP3 module for Apache HTTPD is something that is >> >> desperately needed, noting alternative web servers already offer HTTP3 >> >> support, e.g. NGINX and Caddy. >> >> >> >> Whilst there's evidence of people actively working towards this, e.g. >> >> https://github.com/machine-moon/mod_http3, it's evidently not >> possible >> >> with the current 2.4.x code branch. To that end PR#699 https:// >> >> github.com/apache/httpd/pull/699 has been raised, as a workaround to >> >> allow (some) MPM's to note connections that are not TCP based. >> >> >> >> The following post provides a detailed insight to these issues - >> >> https://codeit.guru/apache-http3-pr-699-mpm-quic-backport-2-4-68 >> >> >> >> We believe it would be really helpful if PR#699 could be approved for >> >> subsequent 2.4.x releases, and equally whether similar functionality >> >> could be added to mpm_winnt, so support for HTTP3 could be developed >> >> for Windows platforms too. >> >> >> >> --- >> >> >> >> Regards >> >> >> >> Steffen Pete >> >> >> -- >> Cheers >> >> Jean-Frederic >> > > > -- > > Best regards, > Alexander Gerasimov > CIO > CodeIT > > *W*: www.codeit.us <https://codeit.us/> >
