Marcello Seri

The culprit should be this call in conduit-lwt-unix mentioned in the report: https://github.com/mirage/ocaml-conduit/blob/a2f91d0fb17c9b0a8436dd39c4267b9144f0bdea/src/conduit-lwt-unix/resolver_lwt_unix.ml#L46 A temporary fix is to make sure you have the /etc/services file, I have asked to reopen...

//cc also @dinosaure

Yes. This is still not possible. If I recall correctly this would need some changes at conduit level. We are breaking some apis, any contribution is welcome

@rgrinberg do you have an idea on how to address this in a clean way?

The problem with the finalizer is that we cannot really call Lwt from it, otherwise we are forced to link unix in cohttp-lwt, at least we could not see how...

Partly related issue: https://github.com/mirage/ocaml-cohttp/issues/578

@samoht did your change to use ca-cert somewhat solve this issue?

Just as a curiosity, what happens if you do the same `curl -v http://127.0.0.1:8080/missing` with any of the other cohttp servers?

Could this be related to https://github.com/mirage/ocaml-cohttp/issues/503 ?

I think it may be worth to add this to cohttp documentation, but I would not modify the implementation since it is not incorrect and there is an easy workaround.