We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In case of very large content, we end up pulling the whole thing even though we want to trim it. This can, in turn, lead to timeouts.
Here are some very large URLs to test on
http://get.gamexp.ru/BGO_160224/BGO_20160224-2.bin http://get.gamexp.ru/BGO_160224/BGO_20160224-4.bin http://get.gamexp.ru/BGO_160224/BGO_20160224-6.bin http://get.gamexp.ru/BGO_160224/BGO_20160224-3.bin http://get.gamexp.ru/BGO_160224/BGO_20160224-1.bin http://get.gamexp.ru/BGO_160224/BGO_20160224-5.bin
what's worse, CloseableHTTTPClient calls EntityUtils.consume(entity); so it looks like we are trying to close it twice anyway.
EntityUtils.consume(entity);
The text was updated successfully, but these errors were encountered:
HttpProtocol: no need to close the stream as CloseableHTTPClient does…
7d2e3ac
… it for us. See #463
OKHTTP can handle that, not HTTP client. Won't fix
Sorry, something went wrong.
See https://issues.apache.org/jira/browse/HTTPCLIENT-1861
jnioche
No branches or pull requests
In case of very large content, we end up pulling the whole thing even though we want to trim it. This can, in turn, lead to timeouts.
Here are some very large URLs to test on
http://get.gamexp.ru/BGO_160224/BGO_20160224-2.bin
http://get.gamexp.ru/BGO_160224/BGO_20160224-4.bin
http://get.gamexp.ru/BGO_160224/BGO_20160224-6.bin
http://get.gamexp.ru/BGO_160224/BGO_20160224-3.bin
http://get.gamexp.ru/BGO_160224/BGO_20160224-1.bin
http://get.gamexp.ru/BGO_160224/BGO_20160224-5.bin
what's worse, CloseableHTTTPClient calls
EntityUtils.consume(entity);
so it looks like we are trying to close it twice anyway.The text was updated successfully, but these errors were encountered: