[prev in list] [next in list] [prev in thread] [next in thread] 

List:       httpclient-commons-dev
Subject:    [jira] [Created] (HTTPCLIENT-2091) Connect timeout is used instead of socket timeout after a tls upg
From:       "Carter Kozak (Jira)" <jira () apache ! org>
Date:       2020-06-24 11:31:00
Message-ID: JIRA.13313234.1592998256000.325477.1592998260013 () Atlassian ! JIRA
[Download RAW message or body]

Carter Kozak created HTTPCLIENT-2091:
----------------------------------------

             Summary: Connect timeout is used instead of socket timeout after a tls \
upgrade  Key: HTTPCLIENT-2091
                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2091
             Project: HttpComponents HttpClient
          Issue Type: Bug
          Components: HttpClient (async), HttpClient (classic)
    Affects Versions: 5.0.1
            Reporter: Carter Kozak


After a TLS upgrade, the connect timeout is used instead of the configured socket \
timeout. In some configurations this results in unexpected socket timeouts earlier \
than expected.

  

This impacts forward proxies using tunneling (CONNECT approach to pass tls bytes \
through a proxy server as opposed to individual plain http requests) which time out \
after the connect timeout is reached.

This is a regression from hc4 which does not exhibit this issue.

Some details here, where I thought the issues could be related: \
https://issues.apache.org/jira/browse/HTTPCLIENT-2090?focusedCommentId=17143321&page=c \
om.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17143321



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]