Skip to content

[2.4.x] mod_proxy_beacon: Backport the module and the mod_proxy changes it needs from trunk - #994

Open
jimjag wants to merge 1 commit into
apache:2.4.xfrom
jimjag:backport-mod_proxy_beacon
Open

jimjag wants to merge 1 commit into
apache:2.4.xfrom
jimjag:backport-mod_proxy_beacon

Conversation

@jimjag

@jimjag jimjag commented Nov 10, 2026

Copy link
Copy Markdown
Member

Backports mod_proxy_beacon from trunk, with the mod_proxy changes it builds on: the PROXY_WORKER_BEACON status bit (MMN minor 143), atomic updates of the shared worker status, no half-defined worker left behind when ap_proxy_define_worker() fails, and run-time balancer workers added under the balancer locks. This replaces three STATUS proposals: mod_proxy_beacon, "Update the shared worker status word atomically" and "Don't leave a half-defined worker".

The module is opt-in. On 2.4.x the proxy config.m4 limits the module selection to most, so even reallyall leaves it out; it needs --enable-proxy-beacon, which the "Python pytest test suites" job now passes so that the beacon tests already on 2.4.x actually run. It needs apr_siphash.h, so configure refuses it with APR-util older than 1.6.

Trunk: r1934995 r1935040 r1935556 r1938135 r1938912 r1939349 r1939350 r1939351 r1939352 r1939362 r1939364 r1939391 r1939436 r1939481 r1939482 r1939484 r1939487 r1939493, and the docs commits a6d8112 and 1624d94.

jimjag added a commit that referenced this pull request Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant