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.

Sign up for GitHub

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

Jump to bottom

allow http proxy as a configuration option #2

Open
ndushay opened this issue May 1, 2017 · 1 comment
Open

allow http proxy as a configuration option #2

ndushay opened this issue May 1, 2017 · 1 comment

Comments

@ndushay
Copy link
Contributor

ndushay commented May 1, 2017 •
edited
Loading

from Thib's email of 2017-04-28:

" The most important type of configurable behavior is proxying HTTP connections ..."

Apache HttpClient 4 is recommended.

"(The classic daemon uses Apache HttpClient 3 and has been stuck there because behavioral differences between HttpClient 3 and 4 will be disruptive to critical components like the crawler and proxies. That said, we can't stay on 3 forever, so Fernando has done the work of upgrading to 4, we just haven't had sufficient testing time to tease out behavioral changes, especially under load or during various types of network disruptions. This tools can use whatever it wants to make outgoing HTTP connections, including the default Java HTTP stack, but we recommend Apache HttpClient 4. Fernando can provide a primer/demo.)"
@ndushay
Copy link
Contributor Author

ndushay commented May 2, 2017

#18 - get more info from Thib/LOCKSS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ndushay