From heyhgl at gmail.com Mon Sep 1 02:30:48 2025 From: heyhgl at gmail.com (Glen Huang) Date: Mon, 1 Sep 2025 10:30:48 +0800 Subject: Possible to make preread work for QUIC? Message-ID: Hi, I'm experimenting load balancing for a bunch of upstream QUIC servers. I wonder if nginx is the right tool for this? I tried a configuration like this, but when doing curl --http3-only quic2.com, nginx seemed to always send the traffic to the default upstream [::1]:444. pid /run/nginx/nginx.pid; error_log stderr; daemon off; events {} stream { map $ssl_preread_server_name $upstream { default [::1]:444; quic1.com unix:/run/nginx/quic1.sock; quic2.com unix:/run/nginx/quic2.sock; } server { listen 443 reuseport; listen [::]:443 reuseport; ssl_preread on; proxy_pass $upstream; } server { listen 443 udp reuseport; listen [::]:443 udp reuseport; ssl_preread on; proxy_pass $upstream; } } Is my configuration incorrect? Does preread support QUIC? Thanks in advance. From sb at nginx.com Thu Sep 25 14:50:37 2025 From: sb at nginx.com (Sergey Budnevich) Date: Thu, 25 Sep 2025 15:50:37 +0100 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 Message-ID: Hello All NGINX mailman mailing lists are retiring on September 30, as the NGINX development process has moved to GitHub. The mailing lists archives will remain accessible for historical reference at https://mailman.nginx.org You can find our GitHub repo here: https://github.com/nginx/nginx If you have questions about using NGINX or need technical help, visit the NGINX Community Forum at https://community.nginx.org. You can also find announcements, latest content, and our event schedule on the forum. The forum aims to provide an engaging environment to interact with our community. To file bugs, please create a GitHub issue. Subscribe to GitHub for release announcements. To submit a security alert, please report a vulnerability within the nginx GitHub repository, or directly to the F5 Security Incident Response Team at F5SIRT at f5.com. Thank you for being a part of the NGINX community. We appreciate your participation in the mailing lists over the years, and look forward to seeing you on GitHub and the NGINX Community Forum in the future. From paul at stormy.ca Thu Sep 25 16:11:17 2025 From: paul at stormy.ca (Paul) Date: Thu, 25 Sep 2025 12:11:17 -0400 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: References: Message-ID: <1041ce2f-ba42-4983-8eeb-c95492a9c164@stormy.ca> On 9/25/25 10:50, Sergey Budnevich wrote: > Hello > > All NGINX mailman mailing lists are retiring on September 30, as the NGINX > development process has moved to GitHub. The mailing lists archives will remain > accessible for historical reference at https://mailman.nginx.org Sergey: This is not good news. Nginx has ~35% world share of webservers. I am not involved in your moving *development* to GitHub. I am referring to a useful *end-user* community service. I do not know if Igor Sysoev and Max Dounin will see this email. I sincerely trust, as a strictly non-politician, that freenginx will survive and prosper. Zdrastye Yours aye, Paul > > You can find our GitHub repo here: https://github.com/nginx/nginx > > If you have questions about using NGINX or need technical help, visit > the NGINX Community Forum at https://community.nginx.org. You can also find > announcements, latest content, and our event schedule on the forum. > The forum aims to provide an engaging environment to interact with our > community. > > To file bugs, please create a GitHub issue. > Subscribe to GitHub for release announcements. > > To submit a security alert, please report a vulnerability within the nginx GitHub > repository, or directly to the F5 Security Incident Response Team at F5SIRT at f5.com. > > Thank you for being a part of the NGINX community. We appreciate your participation > in the mailing lists over the years, and look forward to seeing you on GitHub and > the NGINX Community Forum in the future. > _______________________________________________ > nginx mailing list > nginx at nginx.org > https://mailman.nginx.org/mailman/listinfo/nginx > From noloader at gmail.com Thu Sep 25 21:16:15 2025 From: noloader at gmail.com (Jeffrey Walton) Date: Thu, 25 Sep 2025 17:16:15 -0400 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: References: Message-ID: On Thu, Sep 25, 2025 at 10:51 AM Sergey Budnevich wrote: > > All NGINX mailman mailing lists are retiring on September 30, as the NGINX > development process has moved to GitHub. The mailing lists archives will remain > accessible for historical reference at https://mailman.nginx.org > > You can find our GitHub repo here: https://github.com/nginx/nginx > > If you have questions about using NGINX or need technical help, visit > the NGINX Community Forum at https://community.nginx.org. You can also find > announcements, latest content, and our event schedule on the forum. > The forum aims to provide an engaging environment to interact with our > community. > > To file bugs, please create a GitHub issue. > Subscribe to GitHub for release announcements. > > To submit a security alert, please report a vulnerability within the nginx GitHub > repository, or directly to the F5 Security Incident Response Team at F5SIRT at f5.com. > > Thank you for being a part of the NGINX community. We appreciate your participation > in the mailing lists over the years, and look forward to seeing you on GitHub and > the NGINX Community Forum in the future. I agree with Paul . Trying to use GitHub Issues as a mailing list is an absolute disaster. It is the wrong tool for the job. There are no threaded discussions per se. What we will get is a flood of GutHub Notifications, including a lot of unwanted junk for just about every minute action taken. Many of the notifications will be automatically classified as spam by email services, like GMail. So we will have to combine email messages from Inbox+Spam to try to follow a "thread." And a "thread" in GitHub is actually the conversation for an issue, code review, etc. I endure it with WebAuthn and a few other important projects which I try to stay at the bleeding edge. Please do not make me endure it for Nginx. And for completeness, GitHub is fine for issue tracking. Jeff From ralph at ml.seichter.de Thu Sep 25 21:50:52 2025 From: ralph at ml.seichter.de (Ralph Seichter) Date: Thu, 25 Sep 2025 23:50:52 +0200 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: References: Message-ID: * Sergey Budnevich: > All NGINX mailman mailing lists are retiring on September 30, as the > NGINX development process has moved to GitHub. Not only does this come at very short notice, it is also regrettable, in my opinion. GitHub may be a valid choice for your development process, but as a means of communicating with end users seeking support, mailing lists are far better suited. User-to-user communication is also better handled using mailing lists. Also, I find using proper MUAs is much more efficient than GitHub's web browser UI, and they even work in a TTY environment with low bandwidth. Can you not keep the NGINX user mailing list active? That would not interfere with your developer processes on GitHub. -Ralph From manuel.baesler at gmail.com Fri Sep 26 00:09:56 2025 From: manuel.baesler at gmail.com (Manuel) Date: Fri, 26 Sep 2025 02:09:56 +0200 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 Message-ID: <57A6994E-5C82-4DEB-9485-754DA58C9A93@gmail.com> > Am 25.09.2025 um 23:51 schrieb Ralph Seichter : > > * Sergey Budnevich: > >> All NGINX mailman mailing lists are retiring on September 30, as the >> NGINX development process has moved to GitHub. > > Not only does this come at very short notice, it is also regrettable, in > my opinion. > > GitHub may be a valid choice for your development process, but as a > means of communicating with end users seeking support, mailing lists are > far better suited. User-to-user communication is also better handled > using mailing lists. Also, I find using proper MUAs is much more > efficient than GitHub's web browser UI, and they even work in a TTY > environment with low bandwidth. > > Can you not keep the NGINX user mailing list active? That would not > interfere with your developer processes on GitHub. > > -Ralph You have to understand that on GitHub, discussion can be easily locked, blocked and silenced ¯\_(ツ)_/¯ Retiring email is probably the last step in the enshittification playbook ¯\_(ツ)_/¯ RIP. > _______________________________________________ > nginx mailing list > nginx at nginx.org > https://mailman.nginx.org/mailman/listinfo/nginx From foghorn.cult386 at aceecat.org Fri Sep 26 01:56:04 2025 From: foghorn.cult386 at aceecat.org (foghorn.cult386 at aceecat.org) Date: Thu, 25 Sep 2025 18:56:04 -0700 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: <57A6994E-5C82-4DEB-9485-754DA58C9A93@gmail.com> References: <57A6994E-5C82-4DEB-9485-754DA58C9A93@gmail.com> Message-ID: On Fri, Sep 26, 2025 at 02:09:56AM +0200, Manuel wrote: >>> All NGINX mailman mailing lists are retiring on September 30, as >>> the NGINX development process has moved to GitHub. >> Can you not keep the NGINX user mailing list active? That would not >> interfere with your developer processes on GitHub. > You have to understand that on GitHub, discussion can > be easily locked, blocked and silenced ¯\_(ツ)_/¯ I think there is some misunderstanding here, caused in part by unfortunate phrasing by Sergei. They do not suggest to use GH Issues in place of this list; they suggest the forum. I just tried it and it's based on Discourse. Now, I won't be the one to defend the virtues of web forums vs. mailing lists, I'll always prefer a list like yourself; but I will say, of all the flavors of forums out there, Discourse is by far the least awful. -- Ian From ralph at ml.seichter.de Fri Sep 26 05:27:19 2025 From: ralph at ml.seichter.de (Ralph Seichter) Date: Fri, 26 Sep 2025 07:27:19 +0200 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: References: <57A6994E-5C82-4DEB-9485-754DA58C9A93@gmail.com> Message-ID: * foghorn.cult386: > I think there is some misunderstanding here, caused in part by > unfortunate phrasing by Sergei. They do not suggest to use GH Issues > in place of this list; they suggest the forum. I don't recall mentioning GitHub issues in particular? I stand by what I wrote about GH being inferior to mailing lists as a communication medium for end users. Mailing lists have been a proven means of handling this for decades, so why abandon them now, and on short notice? -Ralph From sb at nginx.com Fri Sep 26 12:01:58 2025 From: sb at nginx.com (Sergey Budnevich) Date: Fri, 26 Sep 2025 13:01:58 +0100 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: References: Message-ID: <5BD576F7-147B-4CED-BF1E-CAAC66023F6F@nginx.com> > On 25 Sep 2025, at 22:50, Ralph Seichter wrote: > > * Sergey Budnevich: > >> All NGINX mailman mailing lists are retiring on September 30, as the >> NGINX development process has moved to GitHub. > > Not only does this come at very short notice, it is also regrettable, in > my opinion. Sorry for the short notice, but a year ago my colleague wrote that we plan to shut down the mailing lists after December 31, 2024, and we actually ran them nine months longer: https://mailman.nginx.org/pipermail/nginx/2024-September/R7KBUUNTG3B2QAAMPS6M7YDOSVCMOZD7.html The main reason for decommissioning is the lack of activity in the mailing list — there are months with announcement emails only. GitHub is not a replacement for a mailing list as a place for questions - it is mainly for information about new releases, i.e., an announcements replacement. community.nginx.org is intended as the mailing list replacement, as Ian correctly mentioned. Also it is possible to use RSS feeds for both GitHub and the forum. > > GitHub may be a valid choice for your development process, but as a > means of communicating with end users seeking support, mailing lists are > far better suited. User-to-user communication is also better handled > using mailing lists. Also, I find using proper MUAs is much more > efficient than GitHub's web browser UI, and they even work in a TTY > environment with low bandwidth. > > Can you not keep the NGINX user mailing list active? That would not > interfere with your developer processes on GitHub. > > -Ralph > _______________________________________________ > nginx mailing list > nginx at nginx.org > https://mailman.nginx.org/mailman/listinfo/nginx From srebecchi at kameleoon.com Fri Sep 26 12:35:33 2025 From: srebecchi at kameleoon.com (=?UTF-8?Q?S=C3=A9bastien_Rebecchi?=) Date: Fri, 26 Sep 2025 14:35:33 +0200 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: <5BD576F7-147B-4CED-BF1E-CAAC66023F6F@nginx.com> References: <5BD576F7-147B-4CED-BF1E-CAAC66023F6F@nginx.com> Message-ID: It was really convenient to receive release announcements by mail. Sad :( Le ven. 26 sept. 2025 à 14:02, Sergey Budnevich a écrit : > > > > On 25 Sep 2025, at 22:50, Ralph Seichter wrote: > > > > * Sergey Budnevich: > > > >> All NGINX mailman mailing lists are retiring on September 30, as the > >> NGINX development process has moved to GitHub. > > > > Not only does this come at very short notice, it is also regrettable, in > > my opinion. > > Sorry for the short notice, but a year ago my colleague wrote that we plan > to shut down the mailing lists after December 31, 2024, and we actually > ran them nine months longer: > https://mailman.nginx.org/pipermail/nginx/2024-September/R7KBUUNTG3B2QAAMPS6M7YDOSVCMOZD7.html > > The main reason for decommissioning is the lack of activity in the mailing > list — there are months with announcement emails only. > > GitHub is not a replacement for a mailing list as a place for questions - > it is > mainly for information about new releases, i.e., an announcements > replacement. > > community.nginx.org is intended as the mailing list replacement, as Ian > correctly mentioned. Also it is possible to use RSS feeds for both GitHub > and the forum. > > > > > GitHub may be a valid choice for your development process, but as a > > means of communicating with end users seeking support, mailing lists are > > far better suited. User-to-user communication is also better handled > > using mailing lists. Also, I find using proper MUAs is much more > > efficient than GitHub's web browser UI, and they even work in a TTY > > environment with low bandwidth. > > > > Can you not keep the NGINX user mailing list active? That would not > > interfere with your developer processes on GitHub. > > > > -Ralph > > _______________________________________________ > > nginx mailing list > > nginx at nginx.org > > https://mailman.nginx.org/mailman/listinfo/nginx > _______________________________________________ > nginx mailing list > nginx at nginx.org > https://mailman.nginx.org/mailman/listinfo/nginx > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at mareichelt.com Fri Sep 26 13:15:40 2025 From: ml at mareichelt.com (Markus Reichelt) Date: Fri, 26 Sep 2025 15:15:40 +0200 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: References: Message-ID: <20250926131540.GA2544@pc21.mareichelt.com> * Ralph Seichter wrote: > Can you not keep the NGINX user mailing list active? That would not > interfere with your developer processes on GitHub. +1 From ralph at ml.seichter.de Fri Sep 26 13:22:27 2025 From: ralph at ml.seichter.de (Ralph Seichter) Date: Fri, 26 Sep 2025 15:22:27 +0200 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: <5BD576F7-147B-4CED-BF1E-CAAC66023F6F@nginx.com> References: <5BD576F7-147B-4CED-BF1E-CAAC66023F6F@nginx.com> Message-ID: * Sergey Budnevich: > The main reason for decommissioning is the lack of activity in the > mailing list — there are months with announcement emails only. In other words, the ML servers are not overburdened and could keep chugging along as they have been doing. ;-) > GitHub is not a replacement for a mailing list as a place for > questions - it is mainly for information about new releases, i.e., an > announcements replacement. Well, setting up a custom GitHub watch option for releases could mimic the ML announcements, partially. > community.nginx.org is intended as the mailing list replacement, as > Ian correctly mentioned. Also it is possible to use RSS feeds for both > GitHub and the forum. People might consider me old-fashioned (and I am of an advanced age), but my work is centered around the use of email as much as possible. It is usually the most effective and convenient means of managing/tracking communication. Importantly, email also is available to me offline once received. Forums can't provide that. Mail is delivered to me (pushed), while I need to actively pull information from forums. And while I am aware of forum digests and feeds, they don't work well for me. -Ralph From noloader at gmail.com Fri Sep 26 18:34:16 2025 From: noloader at gmail.com (Jeffrey Walton) Date: Fri, 26 Sep 2025 14:34:16 -0400 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: References: <5BD576F7-147B-4CED-BF1E-CAAC66023F6F@nginx.com> Message-ID: On Fri, Sep 26, 2025 at 9:22 AM Ralph Seichter wrote: > > [...] > People might consider me old-fashioned (and I am of an advanced age), > but my work is centered around the use of email as much as possible. It > is usually the most effective and convenient means of managing/tracking > communication. Importantly, email also is available to me offline once > received. Forums can't provide that. Mail is delivered to me (pushed), > while I need to actively pull information from forums. And while I am > aware of forum digests and feeds, they don't work well for me. The web forum vs mailing list debate got so bad the IETF considered publishing a document to explain why mailing lists are superior to web forums. The thread started at "Fully functional email address" (June 2025), . The list was provided by Rich Kulawiec at . Jeff From ralph at ml.seichter.de Sat Sep 27 18:21:47 2025 From: ralph at ml.seichter.de (Ralph Seichter) Date: Sat, 27 Sep 2025 20:21:47 +0200 Subject: Important Announcement: All NGINX mailman mailing lists are retiring on September 30 In-Reply-To: References: <5BD576F7-147B-4CED-BF1E-CAAC66023F6F@nginx.com> Message-ID: * Jeffrey Walton: > The list was provided by Rich Kulawiec at > . Thank you for pointing out this comprehensive list. Having used mailing lists since the 1980s, I have not yet seen a replacement which offers so many advantages. New and fancy counts for naught when the proven medium of mailing lists is just so practical. -Ralph