HTTPCLIENT-883: SO_TIMEOUT is not reset on persistent (re-used) connections
git-svn-id: https://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk@829806 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
96b8e1d936
commit
9a5dac386f
|
@ -1,6 +1,9 @@
|
|||
Changes since 4.0
|
||||
-------------------
|
||||
|
||||
* [HTTPCLIENT-883] SO_TIMEOUT is not reset on persistent (re-used) connections.
|
||||
Contributed by Oleg Kalnichevski <olegk at apache.org>
|
||||
|
||||
* [HTTPCLIENT-882] Auth state is not correctly updated if a successful NTLM
|
||||
authentication results in a redirect. This is a minor bug as HttpClient manages
|
||||
to recover from the problem automatically.
|
||||
|
|
|
@ -380,7 +380,9 @@ public class DefaultRequestDirector implements RequestDirector {
|
|||
// Reopen connection if needed
|
||||
if (!managedConn.isOpen()) {
|
||||
managedConn.open(route, context, params);
|
||||
}
|
||||
} else {
|
||||
managedConn.setSocketTimeout(HttpConnectionParams.getSoTimeout(params));
|
||||
}
|
||||
|
||||
try {
|
||||
establishRoute(route, context);
|
||||
|
|
Loading…
Reference in New Issue