Thanks a lot!
I've made a hack which puts the suspeded connection back in the queue:
https://gist.github.com/ArtemGr/9887564
with that the test case works! (`ab` no longer timeouts).
Would it make sense to submit a feature request along these lines?
Should I make a patch or leave it to the more
Please open a bug
for the issue. trunk also has a facility to get called back when a
socket is readable, mod_proxy_wstunnel uses it. It really needs a timeout
to be useful.
I've come up with an (almost) working SUSPENDED test case:
https://gist.github.com/ArtemGr/9870554
It works in browser and with curl -v http://127.0.0.1/sustest;, at least
for some time.
Apache version is 2.4.7 (Debian Jessie).
Problem is, when I test it with ab (ab -n 999 -c 9
Without looking at it too deeply, It seems like suspendable handlers
(that continue on as HTTP) are not really working.
When your timed callback ends, the underlying socket is not in the
keepalive queue anymore in the MPM. The way it normally gets back
into that queue is by ap_process_request
