PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
[ start all new proposals below, under PATCHES PROPOSED. ]
-
+ * mod_proxy: Fix pool usage by protecting w/ a mutex
+ trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1480627
+ http://svn.apache.org/viewvc?view=revision&revision=1482859
+ http://svn.apache.org/viewvc?view=revision&revision=1483190
+ http://svn.apache.org/viewvc?view=revision&revision=1484343
+ http://svn.apache.org/viewvc?view=revision&revision=1500437
+ 2.4.x patch: trunk works, modulo CHANGES
+ +1: jim, minfrin, sf
PATCHES PROPOSED TO BACKPORT FROM TRUNK:
[ New proposals should be added at the end of the list ]
-0.5: sf: I would prefer if this sat in trunk for a few months first
to receive more testing.
- * mod_proxy: Fix pool usage by protecting w/ a mutex
- trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1480627
- http://svn.apache.org/viewvc?view=revision&revision=1482859
- http://svn.apache.org/viewvc?view=revision&revision=1483190
- http://svn.apache.org/viewvc?view=revision&revision=1484343
- http://svn.apache.org/viewvc?view=revision&revision=1500437
- 2.4.x patch: trunk works, modulo CHANGES
- +1: jim, minfrin
- sf says:
- - ap_proxy_sync_balancer() seems to use conf->pool in several
- places, but only one place is protected by conf->mutex.
- I don't think this is correct.
- Also, I can't find any place where conf->mutex is initialized.
- jj says:
- - conf->pool is used in 2 places, both are now protected
- sf says:
- - ap_proxy_initialize_worker() is called from proxy_handler() with
- conf->pool. I guess this should also be mutex protected?
- jj says:
- - it is: ap_proxy_initialize_worker() uses the mutex internally.
- (line ~1735)
-
-
* mod_proxy_http: Make the proxy-interim-response environment variable
effective by formally overriding origin server behaviour.
trunk patch: http://svn.apache.org/r1483027