[ https://issues.apache.org/jira/browse/HTTPCLIENT-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913301#comment-16913301 ]
Jang Ryeol commented on HTTPCLIENT-1765: ---------------------------------------- Yeah adding readTimeout is not that hard. I thought it has so unreasonable default that it might be a bug - but it seems no one cares. Anyway thanks for the help. Regards, Jang Ryeol > SSLConnectionSocketFactory uses connectTimeout for read timeout > --------------------------------------------------------------- > > Key: HTTPCLIENT-1765 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1765 > Project: HttpComponents HttpClient > Issue Type: Bug > Components: HttpClient (classic) > Affects Versions: 4.5 > Environment: Any > Reporter: SATISH BURNWAL > Priority: Major > Labels: features > > SSLConnectionSocketFactory uses connect timeout value for socket.soTimeout as > well (as per the code in SSLConnectionsocketFactory). Because of this, when > clients are created with such config (below), read timeout is not taking > effect. > RequestConfig.Builder rb = RequestConfig.custom(); > rb.setConnectTimeout(3000); > rb.setExpectContinueEnabled(true); > rb.setSocketTimeout(10000); > rb.setAuthenticationEnabled(true); -- This message was sent by Atlassian Jira (v8.3.2#803003) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org