SocketHttpClientConnection does not support socket timeouts while reading
response header
-----------------------------------------------------------------------------------------
Key: HTTPCORE-191
URL: https://issues.apache.org/jira/browse/HTTPCORE-191
Project: HttpComponents HttpCore
Issue Type: Bug
Components: HttpCore
Affects Versions: 4.0
Reporter: Adam Bryzak
Similar to HTTPCORE-190, SocketHttpClientConnection, or more specifically
AbstractHttpClientConnection.receiveResponseHeader() does not store state of
the current request being read, meaning a SocketTimeoutException occurring
while reading the status line or any of the headers will cause a retry to start
reading the next part of the data as if it were the status line when the call
is retried.
This is not causing an issue for me personally. I only spotted it when I was
testing the fix to HTTPCORE-190 by writing the response 1 byte at a time with a
timeout being caused for each byte. I am unsure of any web servers that may
have a delay when writing the status line and/or headers that would cause a
timeout.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
