My bad. I thought you were referring to the socket timout setting. You will have to upgrade to HttpClient 4.0 to be able to set connect timout on the HTTP request level.
Oleg "asolodin" <[email protected]> wrote: > > >olegk wrote: >> >> Andrei, >> >> Socket timeout can be set either on the HTTP agent or the HTTP >request >> level. >> >> You can set a different socket timeout value on each HTTP request >> depending on kind of a target host it is going to be executed >against. >> >> Hope this helps >> >> Oleg >> > >Oleg, thank you for your reply. Just to make sure we are on the same >page, I >was talking about the http.connection.timeout property, which according >to >the documentation can be specified through: global -> client -> >connection >manager -> connection. I don't see a way to specify a connection >timeout on >the method, other than through a name/value. But then I don't see where >in >the code the connection would be using the value passed in the method. >Regarding the SO_TIMEOUT, I do see how the value in method overrides >the one >in the connection, this is in HttpMethodDirector.applyConnectionParams. >I am >looking for similar logic for http.connection.timeout property. > >Thank you. > >-- >View this message in context: >http://old.nabble.com/Connection-timeout-per-host--tp30004821p30011897.html >Sent from the HttpClient-User mailing list archive at Nabble.com. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
