> Another approach could be to "stutter" the blocking backend reads in > mod_proxy_http with a 5 sec socket timeout or so, only to check > frontend->aborted and read again. That might be a minimum effort approach for > the short term.
Unfortunately I don't think you will find frontend->aborted is set in such a case (w HTTP 1.x at least). There is nobody watching while the request is being processed. If you split up the long poll, you still have to do _something_ with the frontend socket to discover it's unusable.
