GitHub user agherardi opened a pull request:

    https://github.com/apache/httpcomponents-core/pull/57

    Workaround for misbehaved servers that return HTTP 204 responses with a 
content

    I have encountered a server that incorrectly returns a content on a HTTP 
204 response. The server also returns a Content-length header with the response.
    
    httpclient assumes that HTTP 204 responses have no content, so it doesn't 
consume the content.
    
    If the connection is reused, this causes httpclient to hang when looking 
for the status line of the next response.
    
    This patch attempts to prevent the issue by allowing HTTP 204 responses 
with Content-length or Transfer-encoding: Chunked as responses to have a 
content.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/agherardi/httpcomponents-core nocontent

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/httpcomponents-core/pull/57.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #57
    
----
commit c4780e32c3a67fe7fd82da8fd9bc2d2d4b240876
Author: alessandro.gherardi <alessandro.gherardi@...>
Date:   2018-01-19T18:39:27Z

    Workaround for misbehaved servers that return HTTP 204 responses with a 
content

----


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to