I want to add that I have learned so much by following the nginx mailing list for more than a decade.
Can we give a huge round of applause to Maxim Dounin for community support and technical excellence?
Maxim and team are answering the deepest of technical questions patiently, to the point.
Every time I read into those threads I am impressed by Maxim. By his dry communication style, his precision, and his patience. It's inspiring.
When you get his reply (which is likely to be the case), you typically get the problem you presented described in his words: with precise language/terms. Very likely he provides a solution. Or a precise quote of reference docs or spec describing why something doesn't work, conceptually. Or a patch (he often replies with "here's a patch that should work", showing a clean diff).
So: https://mailman.nginx.org/pipermail/nginx/ -- highly recommended if you want to learn more about HTTP and web servers in general.
By the way: for forcing DNS re-resolution (mentioned in this thread here) in the open source version by the way there is a weird but extremely powerful workaround (which really works, we have used it in DC/OS successfully over years), also see https://github.com/dcos/dcos/tree/master/packages/adminroute....
It was of course Maxim who described this little trick in the mailing list in 2011 :-)
https://forum.nginx.org/read.php?2,215830,215832#msg-215832
It's still highly relevant in 2023 for controlled dynamic service discovery with nginx.
Can we give a huge round of applause to Maxim Dounin for community support and technical excellence?
Maxim and team are answering the deepest of technical questions patiently, to the point.
Every time I read into those threads I am impressed by Maxim. By his dry communication style, his precision, and his patience. It's inspiring.
When you get his reply (which is likely to be the case), you typically get the problem you presented described in his words: with precise language/terms. Very likely he provides a solution. Or a precise quote of reference docs or spec describing why something doesn't work, conceptually. Or a patch (he often replies with "here's a patch that should work", showing a clean diff).
So: https://mailman.nginx.org/pipermail/nginx/ -- highly recommended if you want to learn more about HTTP and web servers in general.
By the way: for forcing DNS re-resolution (mentioned in this thread here) in the open source version by the way there is a weird but extremely powerful workaround (which really works, we have used it in DC/OS successfully over years), also see https://github.com/dcos/dcos/tree/master/packages/adminroute....
It was of course Maxim who described this little trick in the mailing list in 2011 :-) https://forum.nginx.org/read.php?2,215830,215832#msg-215832
It's still highly relevant in 2023 for controlled dynamic service discovery with nginx.