[
https://issues.apache.org/jira/browse/HTTPCLIENT-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940534#comment-16940534
]
Richard Hernandez commented on HTTPCLIENT-2017:
-----------------------------------------------
[~olegk] Here's a simple test which reproduces it:
https://gist.github.com/rhernandez35/c7bda8de618e21ad06eb40b5ffc3fdb6
Change {{HEAD}} to {{GET}} and it no longer fails with a
{{ConnectionClosedException}}.
> HttpClient5 double-closes IOSessions for HTTP/1.1 HEAD requests
> ---------------------------------------------------------------
>
> Key: HTTPCLIENT-2017
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2017
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Reporter: Richard Hernandez
> Priority: Major
>
> HttpClient5 consistently fails HEAD requests that have the "Connection:
> close" header on the response because the runtime always attempts to close
> the IOSession handling the connection twice. The second close triggers a
> ConnectionClosedException, causing the request to fail.
> For some reason, this only affects HEAD requests. All other HTTP methods work
> fine.
> I don't have a repro that I can share yet, but I'm working on a fix. I'm
> letting you know because I don't know if I'll need to make any changes in
> core (I suspect I will). Can you wait to release beta9 until I have a root
> cause?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
