Stefan Groschupf wrote:
However in case it is known as buggy, we may should not set up as
default http protocol plugin as it is by today.
+1
I have found protocol-http to be more reliable for large crawls than
protocol-httpclient and would be in favor of switching the default back
to protocol-http. When folks need advanced features then they can
switch to protocol-httpclient. Thoughts?
A related issue is that these two plugins replicate a lot of code. At
some point we should try to fix that. See:
http://www.nabble.com/protocol-http-versus-protocol-httpclient-t521282.html
Doug
