New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Idea: combining with free nginx #74
Comments
Hi. We are definitely looking for cooperation. As soon there will be valuable changes in freenginx we'll be happy to integrate them in Angie as well. But there is actually not so much overlap. Having a lot of experience with Maxim in the past, I'd rather say that we have quite different views of nginx future. And I dare say, under his control there wouldn't be a half of features that Angie currently provides over nginx. Note that for the last 10+ years nginx was under almost full control of Maxim, and the current shape of nginx, like it or not, mostly obligates to his views. |
Thanks for your reply. And giving me more insights. Would it not be cool if you list some of those most important extensions that Angie delivers which isn't part of nginx/free and nginx on your Readme? Because not all people click on the documentation link. Edit: nginx also support http3 protocol? So maybe that isn't a feature anymore. |
Our initial intention was to keep this on one place eliminating “out-of-sync” issues. On the other hand, probably you're right and it will be more attractive to have such information straight on the README page. Will consider this, thank you.
nginx doesn't support HTTP/3 on both sides, it can only receive HTTP/3 connections, but cannot proxy requests over HTTP/3. Angie supports both, see here: https://angie.software/en/http_proxy/#proxy-http-version Also, we tried to donate this functionality to nginx, but without any progress so far: https://mailman.nginx.org/pipermail/nginx-devel/2023-December/THMZAQ36SN5BICJSCLX6FLEUI45FHR4H.html - only got quite skeptical response from Maxim. |
Thanks for giving me more insides and answering my questions. I will close it for now. |
Just some idea / brainstorm. Since free nginx was also recently created by another core developer.
Would it not be a good idea to combine the time & effort? I mean, I see a lot of overlap.
I personally don't know how good the relationship is between these two projects. But please consider it since I believe we more or less want to achieve the same together: a free and good nginx replacement.
The text was updated successfully, but these errors were encountered: