Skip to content
New issue

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

HTTP Protocol reads the whole content when calling close() on the stream #463

Closed
jnioche opened this issue May 8, 2017 · 2 comments
Closed

Comments

@jnioche
Copy link
Contributor

jnioche commented May 8, 2017

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.

@jnioche
Copy link
Contributor Author

jnioche commented May 30, 2017

OKHTTP can handle that, not HTTP client. Won't fix

@jnioche jnioche closed this as completed May 30, 2017
@jnioche
Copy link
Contributor Author

jnioche commented Jul 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant