On Mon, Jul 12, 2021 at 10:01 AM Joe Orton <[email protected]> wrote: > > Thread 1 (Thread 0x7f101cff1700 (LWP 3534)): > 3622#0 ap_proxy_acquire_connection > (proxy_function=proxy_function@entry=0x7f105467de9f "http", > conn=conn@entry=0x7f101cff0a88, worker=worker@entry=0x55e9deb5c710, > s=0x55e9def94a58) at proxy_util.c:2484 > 3623#1 0x00007f105467bb5f in proxy_http_handler (r=0x7f0ff40234a0, > worker=0x55e9deb5c710, conf=0x55e9decd0e98, url=0x7f0ff400d1c0 > "http://localhost:8529/";, proxyname=0x0, proxyport=<optimized out>) at > mod_proxy_http.c:1920 > 3624#2 0x00007f1054c9be0c in proxy_run_scheme_handler > (r=r@entry=0x7f0ff40234a0, worker=0x55e9deb5c710, > conf=conf@entry=0x55e9decd0e98, url=0x7f0ff400d1c0 "http://localhost:8529/";, > proxyhost=proxyhost@entry=0x0, proxyport=proxyport@entry=0) at > mod_proxy.c:3479 > 3625#3 0x00007f1054c9de7e in proxy_handler (r=0x7f0ff40234a0) at > mod_proxy.c:1521 > 3626#4 0x000055e9dcff8480 in ap_run_handler (r=r@entry=0x7f0ff40234a0) at > config.c:169 > > this is new?
Should be fixed in r1891477, I can't reproduce anymore with this patch applied. Cheers; Yann.
