[
https://issues.apache.org/jira/browse/HTTPCORE-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646166#comment-16646166
]
David Maplesden commented on HTTPCORE-559:
------------------------------------------
[~olegk] thanks for the quick follow up. Happy to help out.
> The DefaultBHttpClientConnection will not read a simple end-of-stream
> terminated HTTP response body
> ---------------------------------------------------------------------------------------------------
>
> Key: HTTPCORE-559
> URL: https://issues.apache.org/jira/browse/HTTPCORE-559
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore
> Affects Versions: 5.0-beta3
> Reporter: David Maplesden
> Priority: Major
> Fix For: 5.0-beta4
>
>
> When you use the Classic HttpClient to execute a GET request for a resource
> which is returned with no Content-Length or Transfer-Encoding header then the
> response body (which should be now terminated by the closing of the stream)
> is not read. Instead the client returns an empty response with no attempt
> made to read from the stream.
> I realize that virtually no responses are ever sent this way, they almost
> always either have a content length or use chunked transfer encoding, but it
> is still legal as per the HTTP spec to return a response without using either
> of these and relying on the end-of-stream to terminate the response body.
> Currently if a server is doing this, the HttpClient won't receive the
> response.
> I found this problem testing the HttpClient, but I believe the root source of
> the problem is in the DefaultBHttpClientConnection implementation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
