[
https://issues.apache.org/jira/browse/HTTPASYNC-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733106#comment-16733106
]
Oleg Kalnichevski commented on HTTPASYNC-146:
---------------------------------------------
bq. Your original case need to call twice "messageParser.fillBuffer(channel)",
Yes, it does. This is how non-blocking input works. One read it required to get
the data and another one to get `end-of-stream` status. As far as I can tell my
test case is perfectly valid.
> Can't handle the response for the remote server send response and close
> connection
> ----------------------------------------------------------------------------------
>
> Key: HTTPASYNC-146
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-146
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.1.3
> Reporter: Eric Lan
> Priority: Major
>
> When the server return response, such as HTTP 301 for redirect, and close
> the connection.
> The AbstractMessageParser#parse will return null.
> {code}
> HTTP/1.1 301 Moved\r\nLocation: /redirect\r\n
> {code}
> *Notice: there is no last \r\n to mark there is no more headers but the
> server close the connection*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
