[
https://issues.apache.org/jira/browse/HTTPCLIENT-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1930.
-------------------------------------------
Resolution: Invalid
[~wcruppel] William, it is intentional. Request level parameters apply only
once the connection route has been fully established. Please use
{{SocketConfig}} if you need to configure connection level parameters.
> Socket timeout is not honored on proxy "CONNECT" request
> --------------------------------------------------------
>
> Key: HTTPCLIENT-1930
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1930
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.5.5
> Environment: Oracle Linux/RHEL 7.5
> Reporter: William Ruppel
> Priority: Minor
> Attachments: stack_trace.txt
>
>
> I have set a socket timeout on my request, but I've discovered that the
> socket timeout is not honored when a proxy is being used and the proxy does
> not respond to the "CONNECT" command. See the attached stack trace, and note
> the call in
> org.apache.http.impl.execchain.MainClientExec.createTunnelToTarget - this is
> the request that does not timeout. Thanks.
> It's trivial to reproduce this by using Fiddler as the proxy, with Fiddler
> configured to break before requests (Rules->Automatic Breakpoints->Before
> Requests).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
