Irmin_http_unix.Http_clientSourceinclude module type of Cohttp_lwt_unix.Clientinclude Cohttp_lwt.S.Client with type ctx = Cohttp_lwt_unix__.Net.ctxtype ctx = Cohttp_lwt_unix.Net.ctxIn most cases you should use the more specific helper calls in the interface rather than invoke this function directly. See head, get and post for some examples.
include Cohttp.Generic.Client.S
with type 'a io = 'a Lwt.t
and type body = Cohttp_lwt__.Body.t
and type 'a with_context = ?ctx:ctx -> 'atype 'a io = 'a Lwt.ttype 'a with_context = ?ctx:ctx -> 'aval map_context : 'a with_context -> ('a -> 'b) -> 'b with_contextval call :
(?headers:Http.Header.t ->
?body:body ->
?chunked:bool ->
Http.Method.t ->
Uri.t ->
(Http.Response.t * body) io)
with_contextcall ?headers ?body ?chunked meth uri
val head : (?headers:Http.Header.t -> Uri.t -> Http.Response.t io) with_contextval get :
(?headers:Http.Header.t -> Uri.t -> (Http.Response.t * body) io) with_contextval delete :
(?body:body ->
?chunked:bool ->
?headers:Http.Header.t ->
Uri.t ->
(Http.Response.t * body) io)
with_contextval post :
(?body:body ->
?chunked:bool ->
?headers:Http.Header.t ->
Uri.t ->
(Http.Response.t * body) io)
with_contextval put :
(?body:body ->
?chunked:bool ->
?headers:Http.Header.t ->
Uri.t ->
(Http.Response.t * body) io)
with_contextval patch :
(?body:body ->
?chunked:bool ->
?headers:Http.Header.t ->
Uri.t ->
(Http.Response.t * body) io)
with_contextProvide a function used to process requests. Please see call. The provided function is only used when no ctx argument is passed to the convenience functions below.
val post_form :
?ctx:ctx ->
?headers:Http.Header.t ->
params:(string * string list) list ->
Uri.t ->
(Http.Response.t * Cohttp_lwt__.Body.t) Lwt.tval callv :
?ctx:ctx ->
Uri.t ->
(Http.Request.t * Cohttp_lwt__.Body.t) Lwt_stream.t ->
(Http.Response.t * Cohttp_lwt__.Body.t) Lwt_stream.t Lwt.tval custom_ctx :
?ctx:Conduit_lwt_unix.ctx ->
?resolver:Resolver_lwt.t ->
unit ->
Cohttp_lwt_unix.Net.ctxcustom_ctx ?ctx ?resolver () will return a context that is the same as the default_ctx, but with either the connection handling or resolution module overridden with ctx or resolver respectively. This is useful to supply a Conduit_lwt_unix.ctx with a custom source network interface, or a Resolver_lwt.t with a different name resolution strategy (for instance to override a hostname to point it to a Unix domain socket).