[
https://issues.apache.org/jira/browse/HTTPCORE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941591#comment-16941591
]
ASF subversion and git services commented on HTTPCORE-604:
----------------------------------------------------------
Commit 5d7d11bf87e8445cdb3a00562e2d7df7d6364544 in httpcomponents-core's branch
refs/heads/master from Oleg Kalnichevski
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-core.git;h=5d7d11b ]
HTTPCORE-604: async HTTP/1.1 protocol handler must close the i/o session if it
cannot be kept alive before passing control to the message exchange hanlder
> HttpClient5 double-closes IOSessions for HTTP/1.1 HEAD requests
> ---------------------------------------------------------------
>
> Key: HTTPCORE-604
> URL: https://issues.apache.org/jira/browse/HTTPCORE-604
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Reporter: Richard Hernandez
> Priority: Major
> Fix For: 5.0-beta9
>
>
> 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]
