On Fri, Jun 24, 2016 at 1:10 AM, William A Rowe Jr <[email protected]> wrote:
> Once we are happy shipping httpd-2.4.23, I'm planning to change > the behavior of trunk by eliminating this whole mess... > One bit of historical perspective by readers who are confused why we came to this point in the first place... httpd-2.2.2 behavior; ./configure checking whether to enable mod_proxy... no checking whether to enable mod_proxy_connect... no checking whether to enable mod_proxy_ftp... no checking whether to enable mod_proxy_http... no checking whether to enable mod_proxy_ajp... no checking whether to enable mod_proxy_balancer... no ./configure --enable-mods-shared=most checking whether to enable mod_proxy... no checking whether to enable mod_proxy_connect... no checking whether to enable mod_proxy_ftp... no checking whether to enable mod_proxy_http... no checking whether to enable mod_proxy_ajp... no checking whether to enable mod_proxy_balancer... no ./configure --enable-mods-shared=most --enable-proxy checking whether to enable mod_proxy... shared (most) checking whether to enable mod_proxy_connect... shared (most) checking whether to enable mod_proxy_ftp... shared (most) checking whether to enable mod_proxy_http... shared (most) checking whether to enable mod_proxy_ajp... shared (most) checking whether to enable mod_proxy_balancer... shared (most) httpd-2.4.1 behavior; ./configure checking whether to enable mod_proxy... shared (most) checking whether to enable mod_proxy_connect... checking dependencies checking whether to enable mod_proxy_connect... shared (most) checking whether to enable mod_proxy_ftp... checking dependencies checking whether to enable mod_proxy_ftp... shared (most) checking whether to enable mod_proxy_http... checking dependencies checking whether to enable mod_proxy_http... shared (most) checking whether to enable mod_proxy_fcgi... checking dependencies checking whether to enable mod_proxy_fcgi... shared (most) checking whether to enable mod_proxy_scgi... checking dependencies checking whether to enable mod_proxy_scgi... shared (most) checking whether to enable mod_proxy_fdpass... no checking whether to enable mod_proxy_ajp... checking dependencies checking whether to enable mod_proxy_ajp... shared (most) checking whether to enable mod_proxy_balancer... checking dependencies checking whether to enable mod_proxy_balancer... shared (most) checking whether to enable mod_proxy_express... checking dependencies checking whether to enable mod_proxy_express... shared (most) Earlier in the 2.x development schema, the proxy module had just been re-factored and re-introduced, and carried the baggage of only five subordinate modules. By 2.4 we recognized the refactored mod_proxy as stable enough to promote to the default 'most' configuration, with 9 subordinate proxy modules. In 2.4.21+ we are up to 11 subordinate modules. What was once a quick-solution in httpd 2.2 proxy/modules/config.m4 has outlived its usefulness, and the ./configure defaults in trunk/ make that whole overloaded --enable-proxy unnecessary in any 2.next release. That's why I suggest we keep this cleaned-up logic for the lifespan of the 2.4 branch (not breaking anyone's expected ./configure syntax), and axe it on trunk next week.
