Hello, Sometimes custom module developers need to iterate over configured location(s), configured in some or all server(s) blocks. For example, to perform post-initialization steps, defined by custom directives in their modules. Now it is virtually impossible.
I've posted question about this matter few years ago: https://mailman.nginx.org/pipermail/nginx-devel/2016-October/008882.html Since then, I received quite a few private emails about whether I succeeded in my findings. So, I'm not alone, who faced this issue. Fortunately, the described goal could be easily achieved by making just internal proxy modules structures available in a separate header. After that implementation of desired functionality is just a matter of writing a few lines of code. Patches а following. No functional changes, just code movement from .c to .h files. Development community, at least through my voice, will be grateful to see them applied to the latest development branch. -- Cheers, Andrey
_______________________________________________ nginx-devel mailing list nginx-devel@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx-devel
