AuthorsAnil Madhavapeddy, Thomas Leonard and Thomas Gazagnaire
Issue Trackerhttps://github.com/mirage/ocaml-conduit/issues
cstruct>= 3.0.0
jbuilder>= 1.0+beta10
mirage-dns>= 3.0.0
mirage-flow-lwt>= 1.2.0
mirage-types-lwt>= 3.0.0
tls>= 0.8.0
vchan>= 3.0.0
Availableocaml-version >= "4.03.0"
PublishedJul 23, 2017
Source [http] https://github.com/mirage/ocaml-conduit/releases/download/v1.0.0/conduit-1.0.0.tbz
StatisticsInstalled 3 times last month.

Network conduit library

The conduit library takes care of establishing and listening for TCP and SSL/TLS connections for the Lwt and Async libraries.

The reason this library exists is to provide a degree of abstraction from the precise SSL library used, since there are a variety of ways to bind to a library (e.g. the C FFI, or the Ctypes library), as well as well as which library is used (just OpenSSL for now).

By default, OpenSSL is used as the preferred connection library, but you can force the use of the pure OCaml TLS stack by setting the environment variable CONDUIT_TLS=native when starting your program.


Source code is in lib/.

  • Conduit_lwt_unix has the Lwt UNIX modules.
  • Conduit_async has the Core/Async modules.

There are also resolvers that map URIs to Conduit endpoints. See http://mirage.github.io/ocaml-conduit/ for the online ocamldoc for more details.


Some of the Lwt_unix-based modules use a non-empty CONDUIT_DEBUG environment variable to output debugging information to standard error. Just set this variable when running the program to see what URIs are being resolved to.

Further Informartion