Loading STATUS +18 −16 Original line number Diff line number Diff line Loading @@ -125,6 +125,24 @@ PATCHES ACCEPTED TO BACKPORT FROM TRUNK: PATCHES PROPOSED TO BACKPORT FROM TRUNK: [ New proposals should be added at the end of the list ] * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch and ProxyMatch section to distinguish between normal workers and workers with regex substitutions in the name. Implement handling of such workers in ap_proxy_get_worker(). Fixes the bug when regex workers were not matched and used for request. PR 43513. trunk patch: http://svn.apache.org/r1609680 http://svn.apache.org/r1609688 http://svn.apache.org/r1641381 http://svn.apache.org/r1826289 http://svn.apache.org/r1826313 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call). Also added missing r1609688 to the patchset. 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-ap_proxy_define_match_worker-v2.patch +1: ylavic -0: covener tried to review this one in Austin with Jeff. Does the added match function really cover a very narrow set of parameters with the way it skips over backreferences? Also, why a new API vs. just setting the field inline? PATCHES/ISSUES THAT ARE BEING WORKED [ New entries should be added at the START of the list ] Loading Loading @@ -265,22 +283,6 @@ PATCHES/ISSUES THAT ARE STALLED (sorry, haven't finished reviewing completely) jim: What is the status of this?? * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch and ProxyMatch section to distinguish between normal workers and workers with regex substitutions in the name. Implement handling of such workers in ap_proxy_get_worker(). Fixes the bug when regex workers were not matched and used for request. PR 43513. trunk patch: http://svn.apache.org/r1609680 http://svn.apache.org/r1609688 http://svn.apache.org/r1641381 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call). Also added missing r1609688 to the patchset. 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-ap_proxy_define_match_worker.patch +1: ylavic -0: covener tried to review this one in Austin with Jeff. Does the added match function really cover a very narrow set of parameters with the way it skips over backreferences? Also, why a new API vs. just setting the field inline? * core: Add support for systemd socket activation. trunk patch: http://svn.apache.org/r1511033 http://svn.apache.org/r1608686 Loading Loading
STATUS +18 −16 Original line number Diff line number Diff line Loading @@ -125,6 +125,24 @@ PATCHES ACCEPTED TO BACKPORT FROM TRUNK: PATCHES PROPOSED TO BACKPORT FROM TRUNK: [ New proposals should be added at the end of the list ] * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch and ProxyMatch section to distinguish between normal workers and workers with regex substitutions in the name. Implement handling of such workers in ap_proxy_get_worker(). Fixes the bug when regex workers were not matched and used for request. PR 43513. trunk patch: http://svn.apache.org/r1609680 http://svn.apache.org/r1609688 http://svn.apache.org/r1641381 http://svn.apache.org/r1826289 http://svn.apache.org/r1826313 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call). Also added missing r1609688 to the patchset. 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-ap_proxy_define_match_worker-v2.patch +1: ylavic -0: covener tried to review this one in Austin with Jeff. Does the added match function really cover a very narrow set of parameters with the way it skips over backreferences? Also, why a new API vs. just setting the field inline? PATCHES/ISSUES THAT ARE BEING WORKED [ New entries should be added at the START of the list ] Loading Loading @@ -265,22 +283,6 @@ PATCHES/ISSUES THAT ARE STALLED (sorry, haven't finished reviewing completely) jim: What is the status of this?? * mod_proxy: Add ap_proxy_define_match_worker() and use it for ProxyPassMatch and ProxyMatch section to distinguish between normal workers and workers with regex substitutions in the name. Implement handling of such workers in ap_proxy_get_worker(). Fixes the bug when regex workers were not matched and used for request. PR 43513. trunk patch: http://svn.apache.org/r1609680 http://svn.apache.org/r1609688 http://svn.apache.org/r1641381 ylavic: Merge patch provided (reusing new->real to avoid double de_socketfy() call). Also added missing r1609688 to the patchset. 2.4.x patch: http://home.apache.org/~ylavic/patches/httpd-2.4.x-ap_proxy_define_match_worker.patch +1: ylavic -0: covener tried to review this one in Austin with Jeff. Does the added match function really cover a very narrow set of parameters with the way it skips over backreferences? Also, why a new API vs. just setting the field inline? * core: Add support for systemd socket activation. trunk patch: http://svn.apache.org/r1511033 http://svn.apache.org/r1608686 Loading