https://bz.apache.org/bugzilla/show_bug.cgi?id=61499
--- Comment #3 from Dominik Stillhard <[email protected]> --- I tested this in version 2.3.34 and the bug still exists. The problem is, that compare to http checks, in the function ap_proxy_connect_backend (proxy_util.c) the backend_addr is NULL. Thats why we never fall in the while-loop in that case, because ap_proxy_check_connection returns APR_ENOSOCKET then. This is because of this line in the function check_tcp (mod_proxy_hcheck.c): backend->addr = hc->cp->addr; But this is already done in the function hc_get_backend (mod_proxy_hcheck.c), which is called just two lines before: (*backend)->addr = hc->cp->addr; I don’t completely understand why this double-copy leads to backend->addr being NULL, but removing the line solves the problem. I have tested this with http 2.4.34 and tcp checks arrive at the backend server. The patch (based on trunk) simply removes this line, anyway i have attached it. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
