Conversation

nginx's own caching reverse proxy support and other features are far more primitive and they gradually replaced almost all of it with their own code to the point that it's not really nginx anymore. They tried to upstream a bit but it mostly didn't go anywhere and it's too late.
1
A problem with nginx as an open source project is they have an open core model where a bunch of important and even very basic features are part of NGINX Plus instead of open source nginx. Simple example: nginx permanently caches DNS result for each host entry in upstream blocks.
2
I'll believe it when I see it. Their business model is at odds with an open source project accepting contributions, since they get their money from implementing features based on contract work and selling access to features exclusively available in NGINX Plus. Doesn't mix well.
2
1
Probably a mix of both. They probably don't like to maintain a bunch of core features in NGINX Plus. A particularly frustrating thing is that you can see a bunch of stubs for proprietary features in the open source nginx since they do make things convenient for themselves.
1
It's one of those projects that theoretically takes contributions but where in reality it's extremely hard to get them to accept any features not directly requested by their customers and they may want to write it themselves to get paid by them anyway. It's fairly frustrating.
1
My view on what's happening is they see NGINX Unit as eventually replacing nginx so they can treat nginx as a legacy cash cow. This year nginx had no commits from Feb 4th until one on April 29th, then nothing until May 24th. It's back to regular slow entirely internal dev now.
2
1
99% of recent stuff on nginx has been batches of bug fixes split into tiny commits including fixing properly enforcing restrictions on requested URIs and properly handling having multiple headers with same key which was supposed to be handled the same as comma separated values.
1
Show replies