1 patch for repository http://darcs.net/screened:

patch 4f0f6e70180b32c11fe125431ec4de96ced3e764
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Sep 25 19:03:11 CEST 2018
  * new implementation of http client based on http-conduit
  
  This implementation does not use our self-written download manager in
  Darcs.Util.Download, which is needed only to interact with libcurl. Instead,
  speculating on a remote file is done simply by running the action in a
  background thread (using async) and relying on the connection manager that
  is supplied with http-conduit. This works pretty well and gives us the full
  functionality (including HTTPS) in a portable manner, so I switched the
  default for the curl flag in darcs.cabal to False.

Attachments

• new-implementation-of-http-client-based-on-http_conduit.dpatch
• patch-preview.txt
• unnamed

Note that lately I am getting failures for these tests:

network/clone
network/lazy-clone

Its says:

Not a repository: http://hub.darcs.net/kowey/tabular (Problem with the
SSL CA cert (path? access rights?))

With this patch applied I can get http://hub.darcs.net/kowey/tabular
just fine.

Ganesh: could you check that this patch works on Windows? If it does I
would like to screen this patch.

Yes, it does work on Windows. Thank you! All the other Windows breaks 
are forgiven ;-) I've pushed it to screened.

Looks fine. Did you try out the POST functionality? I don't think
it's commonly used though we'd like to use it with darcsden.

I wonder if we can just drop the curl variant completely. Maybe
wait for a release or two to give people time to detect problems 
with the new implementation.

I did not try POST because I have no idea how to set up a test for 
this feature. We should have a regression test for this but I don't 
think we do.

I think in theory you can set up a receiver with contrib/upload.cgi
but I haven't tried to use that for many years. I think we can do
without testing POST for now.