This HTTP implementation uses the Cohttp portable implementaiton
along with the Lwt threading library in order to provide a
Cohttp_mirage functor that can be used in MirageOS unikernels
to build very small and efficient HTTP clients and servers
without having a hard dependency on an underlying operating
Please see https://mirage.io for a self-hosted explanation and instructions on how to use this library.
ocaml-cohttp -- an OCaml library for HTTP clients and servers
Cohttp is an OCaml library for creating HTTP daemons. It has a portable HTTP parser, and implementations using various asynchronous programming libraries:
Cohttp_lwt_unixuses the Lwt library, and specifically the UNIX bindings.
Cohttp_asyncuses the Async library.
Cohttp_lwtexposes an OS-independent Lwt interface, which is used by the Mirage interface to generate standalone microkernels (use the cohttp-mirage subpackage).
You can implement other targets using the parser very easily. Look at the
IO signature in
lib/s.mli and implement that in the desired backend.
You can activate some runtime debugging by setting
COHTTP_DEBUG to any value, and all requests and responses will be written to stderr. Further debugging of the connection layer can be obtained by setting
CONDUIT_DEBUG to any value.
Latest stable version should be obtained from opam. Make sure to install the specific backends you want as well. E.g.
$ opam install cohttp lwt js_of_ocaml
You can also obtain the development release:
$ opam pin add cohttp --dev-repo
Cohttp ships with 6 findlib libraries:
cohttp - Base
Cohttpmodule. No platform specific functionality.
cohttp-async - Async backend
cohttp-lwt-jsoo - Jsoo (XHR) client
cohttp-lwt - Lwt backend without unix specifics.
cohttp-lwt-unix - Unix based lwt backend
cohttp-top - Print cohttp types in the toplevel (
Cohttp provides clients for Async, Lwt, and jsoo (Lwt based). In this tutorial, we will use the lwt client but it should be easily translateable to Async.
To create a simple request, use one of the methods in
call is the most general, there are also http method specialized such as
For example downloading the reddit frontpage:
(* client_example.ml *) open Lwt open Cohttp open Cohttp_lwt_unix let body = Client.get (Uri.of_string "https://www.reddit.com/") >>= fun (resp, body) -> let code = resp |> Response.status |> Code.code_of_status in Printf.printf "Response code: %d\n" code; Printf.printf "Headers: %s\n" (resp |> Response.headers |> Header.to_string); body |> Cohttp_lwt.Body.to_string >|= fun body -> Printf.printf "Body of length: %d\n" (String.length body); body let () = let body = Lwt_main.run body in print_endline ("Received body\n" ^ body)
ocamlbuild -pkg cohttp-lwt-unix client_example.native
There's a few things to notice:
We open 2 modules.
Cohttpcontains the backend independent stuff and
Cohttp_lwt_unixis the lwt + unix specific stuff.
Uri.tand makes an http request.
Client.getalso accepts optional arguments for things like header information.
The http response is returned in a tuple. The first element of the tuple contains the response's status code, headers, http version, etc. The second element contains the body.
The body is then converted to a string and is returned (after the length is printed). Note that
Cohttp_lwt.Body.to_stringhence it's up to us to keep a reference to the result.
We must trigger lwt's event loop for the request to run.
Lwt_main.runwill run the event loop and return with final value of
bodywhich we then print.
Note that in order to request an HTTPS page like in the above example, you'll need Cohttp to have been compiled with SSL or TLS. For SSL, you'll need to install both
lwt_ssl before installing
cohttp. The TLS route will require installing
Consult the following modules for reference:
Docker Socket Client example
Cohttp provides a lot of utilites out of the box, but does not prevent the users to dig in and customise it for their needs. The following is an example of a unix socket client to communicate with Docker.
open Lwt.Infix let t = let resolver = let h = Hashtbl.create 1 in Hashtbl.add h "docker" (`Unix_domain_socket "/var/run/docker.sock"); Resolver_lwt_unix.static h in let ctx = Cohttp_lwt_unix.Client.custom_ctx ~resolver () in Cohttp_lwt_unix.Client.get ~ctx (Uri.of_string "http://docker/version") >>= fun (resp, body) -> let open Cohttp in let code = resp |> Response.status |> Code.code_of_status in Printf.printf "Response code: %d\n" code; Printf.printf "Headers: %s\n" (resp |> Response.headers |> Header.to_string); body |> Cohttp_lwt.Body.to_string >|= fun body -> Printf.printf "Body of length: %d\n" (String.length body); print_endline ("Received body\n" ^ body) let _ = Lwt_main.run t
The main issue there is there no way to resolve a socket address, so you need to create a custom resolver to map a hostname to the Unix domain socket.
Basic Server Tutorial
Implementing a server in cohttp is mostly equivalent to implementing a function of type:
conn -> Cohttp.Request.t -> Cohttp_lwt.Body.t -> (Cohttp.Response.t * Cohttp_lwt.Body.t) Lwt.t
The parameters are self explanatory but we'll summarize them quickly here:
conn- contains connection information
Cohttp.Request.t- Request information such as method, uri, headers, etc.
Cohttp_lwt.Body.t- Contains the request body. You must manually decode the request body into json, form encoded pairs, etc. For cohttp, the body is simply binary data.
Here's an example of a simple cohttp server that outputs back request information.
(* server_example.ml *) open Lwt open Cohttp open Cohttp_lwt_unix let server = let callback _conn req body = let uri = req |> Request.uri |> Uri.to_string in let meth = req |> Request.meth |> Code.string_of_method in let headers = req |> Request.headers |> Header.to_string in body |> Cohttp_lwt.Body.to_string >|= (fun body -> (Printf.sprintf "Uri: %s\nMethod: %s\nHeaders\nHeaders: %s\nBody: %s" uri meth headers body)) >>= (fun body -> Server.respond_string ~status:`OK ~body ()) in Server.create ~mode:(`TCP (`Port 8000)) (Server.make ~callback ()) let () = ignore (Lwt_main.run server)
ocamlbuild -pkg cohttp-lwt-unix server_example.native
The following modules are useful references:
Cohttp_lwt.Server - Common to mirage and Unix
Cohttp_lwt_unix.Server - Unix specific.
Cohttp comes with a few simple binaries that are handy, useful testing cohttp itself, and serve as examples of how to use cohttp. The binaries come in two flavours - Async and Lwt based.
This is a simple curl utility implemented using cohttp. An example of an invocation is:
$ cohttp-curl-lwt -v -X GET "https://www.reddit.com/"
This binary acts in a similar fashion to the Python
SimpleHTTPServer. Just run
cohttp-server-async in a directory and it will open up a local port and serve the files over HTTP.
Assuming that the server is running in cohttp's source directory:
$ cohttp-curl-lwt 'http://0.0.0.0:8080/_oasis'