package cohttp

  1. Overview
  2. Docs
An OCaml library for HTTP clients and servers

Install

Dune Dependency

Authors

Maintainers

Sources

cohttp-0.99.0.tbz
sha256=ad79462819b141e6054ae32560a16fcdfd93a1ab0c0245f801b3791fdbbe2f2e
md5=a789a9ed492005257bdb217e2248da0d

Description

Join the chat at https://gitter.im/mirage/ocaml-cohttp

Cohttp is an OCaml library for creating HTTP daemons. It has a portable HTTP parser, and implementations using various asynchronous programming libraries:

  • Cohttp_lwt_unix uses the Lwt library, and specifically the UNIX bindings.
  • Cohttp_async uses the Async library.
  • Cohttp_lwt exposes an OS-independent Lwt interface, which is used by the Mirage interface to generate standalone microkernels (see the mirage-http repository).
  • Cohttp_lwt_xhr compiles to a JavaScript module that maps the Cohttp calls to XMLHTTPRequests. This is used to compile OCaml libraries like the GitHub bindings to JavaScript and still run efficiently.

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.

Tags

org:mirage org:xapi-project

Published: 25 Jul 2017

README

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_unix uses the Lwt library, and specifically the UNIX bindings.

  • Cohttp_async uses the Async library.

  • Cohttp_lwt exposes an OS-independent Lwt interface, which is used by the Mirage interface to generate standalone microkernels (see the mirage-http repository).

  • Cohttp_lwt_xhr compiles to a JavaScript module that maps the Cohttp calls to XMLHTTPRequests. This is used to compile OCaml libraries like the GitHub bindings to JavaScript and still run efficiently.

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.

Installation

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

Findlib (Ocamlfind)

Cohttp ships with 6 findlib libraries:

  • cohttp - Base Cohttp module. No platform specific functionality.

  • cohttp-async - Async backend Cohttp_async

  • 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 (#require "cohttp-top")

Client Tutorial

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 Cohttp_lwt_unix.Client. call is the most general, there are also http method specialized such as get, post, etc.

For example downloading the reddit frontpage:

(* client_example.ml *)
open Lwt
open Cohttp
open Cohttp_lwt_unix

let body =
  Client.get (Uri.of_string "http://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)

Build with:

ocamlbuild -pkg cohttp-lwt-unix client_example.native

There's a few things to notice:

  • We open 2 modules. Cohttp contains the backend independent stuff and Cohttp_lwt_unix is the lwt + unix specific stuff.

  • Client.get accepts a Uri.t and makes an http request. Client.get also 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_string hence 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.run will run the event loop and return with final value of body which we then print.

Consult the following modules for reference:

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)

Build with:

ocamlbuild -pkg cohttp-lwt-unix server_example.native

The following modules are useful references:

Installed Binaries

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.

  • $ cohttp-curl-{lwt,async}

This is a simple curl utility implemented using cohttp. An example of an invocation is:

$ cohttp-curl-lwt -v -X GET "http://www.reddit.com/"
  • $ cohttp-server-{lwt,async}

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.

$ cohttp-server-async

Assuming that the server is running in cohttp's source directory:

$ cohttp-curl-lwt 'http://0.0.0.0:8080/_oasis'

Important Links

Dependencies (15)

  1. jsonm build
  2. logs
  3. fmt
  4. magic-mime
  5. base64 >= "2.0.0" & < "3.0.0"
  6. stringext
  7. ppx_sexp_conv >= "v0.9.0"
  8. ppx_fields_conv >= "v0.9.0"
  9. sexplib
  10. fieldslib
  11. uri >= "1.9.0" & < "2.0.0"
  12. re
  13. jbuilder >= "1.0+beta10"
  14. base-bytes
  15. ocaml >= "4.03.0" & < "4.06.0"

Dev Dependencies (2)

  1. alcotest with-test
  2. ounit with-test

Used by (67)

  1. aws-async
  2. aws-lwt
  3. aws-s3 >= "2.0.0" & < "4.0.0"
  4. awsm
  5. awsm-codegen
  6. azblob-async
  7. azure-cosmos-db
  8. c3
  9. calculon-web < "0.5"
  10. canary
  11. cca >= "0.6.2"
  12. cohttp-async < "1.0.0" | >= "1.1.1" & < "2.2.0"
  13. cohttp-lwt < "1.0.0"
  14. cohttp-lwt-jsoo != "1.0.0" & < "1.1.1"
  15. cohttp-mirage >= "2.0.0" & != "2.1.1" & < "2.5.5"
  16. cohttp-top < "1.0.0" | >= "1.1.0" & < "2.2.0"
  17. comby-semantic
  18. cowabloga >= "0.0.9" & != "0.2.2"
  19. datakit < "0.10.0"
  20. dblp-api
  21. dropbox >= "0.2"
  22. frenetic >= "3.3.0" & < "5.0.5"
  23. git = "1.4.10" | >= "1.5.0" & < "1.10.0"
  24. git-cohttp
  25. git-paf < "3.5.0"
  26. git-unix < "1.10.0"
  27. github >= "3.0.1" & < "4.4.0"
  28. github-jsoo >= "3.0.1" & < "4.4.0"
  29. github-unix >= "4.2.0" & < "4.4.0"
  30. hockmd
  31. imaplet-lwt >= "0.1.3"
  32. influxdb-async
  33. influxdb-lwt
  34. iocaml < "0.4.8"
  35. ip2location
  36. ip2locationio
  37. ip2whois
  38. irmin >= "0.9.0" & != "0.11.1" & < "1.0.0"
  39. irmin-cli
  40. irmin-graphql >= "2.3.0"
  41. irmin-http >= "2.3.0"
  42. irmin-mirage-git >= "2.3.0" & < "2.8.0"
  43. irmin-unix < "0.9.9" | >= "2.3.0"
  44. letsencrypt < "0.3.0"
  45. links >= "0.7.3"
  46. magic-trace
  47. mechaml >= "1.0.0"
  48. merge-queues >= "0.2.0"
  49. mirage-http = "2.0.0" | >= "3.2.0"
  50. mirage-www >= "1.1.0"
  51. nsq >= "0.2.4"
  52. ocamlapi
  53. oframl
  54. ojs-base >= "0.3.0" & < "0.6.0"
  55. opium = "0.13.3"
  56. opium_kernel
  57. podge
  58. ppx_json_types
  59. prof_spacetime = "0.2.0"
  60. prometheus-app = "0.4"
  61. quests
  62. session-cohttp
  63. sociaml-facebook-api >= "0.4.1"
  64. transmission-rpc
  65. webmachine >= "0.4.0" & < "0.6.0"
  66. websocket = "2.10"
  67. xen-api-client >= "0.9.8" & < "0.9.14"

Conflicts

None

OCaml

Innovation. Community. Security.