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

Investigate OKHTTP to replace Apache HTTPClient #443

Closed
jnioche opened this Issue Mar 24, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@jnioche
Member

jnioche commented Mar 24, 2017

OKHTTP seems to be more robust on a small set of problematic URLs I tested (including #405) and at first glance, its API is more logical and easier to understand.

It would also make it easier to store the http request verbatim (see #317) for generating WARCs.

@jnioche

This comment has been minimized.

Show comment
Hide comment
@jnioche

jnioche May 15, 2017

Member

OKHTTP does not have the same issue as httpclient for large content, see #463. We can read and trim very large content without getting stuck when closing it.

Member

jnioche commented May 15, 2017

OKHTTP does not have the same issue as httpclient for large content, see #463. We can read and trim very large content without getting stuck when closing it.

@jnioche jnioche added this to the 1.6 milestone Jun 22, 2017

@jnioche jnioche closed this in #484 Jul 7, 2017

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