I somehow convinced myself that socketTimeout was for some socket operation, not for the overall 'have we received a response to this request'.
I may offer you a doc patch. On Sat, Jan 2, 2016 at 12:12 PM, Oleg Kalnichevski <ol...@apache.org> wrote: > On Fri, 2016-01-01 at 16:04 -0500, Benson Margulies wrote: >> I've spent some time reading the code, and I'm stumped as to how to >> arrange for a timeout on getting a response back with the async >> client. I see how to configure the connect timeout with RequestConfig. >> I'm on 4.4.1. I'm using callbacks, not the returned futures, so it >> would be some coding to make my own arrangements. >> > > Hi Benson > Should not RequestConfig#socketTimeout be what you want? > > Oleg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org > For additional commands, e-mail: httpclient-users-h...@hc.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
