Cohttp_lwt_unix.ClientTheClient module implements the full UNIX HTTP client interface, including the UNIX-specific functions defined inC.
includeCohttp_lwt.S.Clientwithtypectx =Net.ctxtype ctx =Net.ctxIf provided, no connection cache is used, butConnection_cache.Make_no_cache.create is used to resolve uri and create a dedicated connection withctx.
In most cases you should use the more specific helper calls in the interface rather than invoke this function directly. Seehead,get andpost for some examples.
includeCohttp.Generic.Client.Swithtype'aio ='aLwt.tandtypebody =Cohttp_lwt.Body.tandtype'awith_context =?ctx:ctx->'atype'a with_context =?ctx:ctx->'atype body =Cohttp_lwt.Body.tval map_context :'awith_context->('a->'b)->'bwith_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
(response, response_body) Consumeresponse_body in a timely fashion. Please seecall about how and why.
use chunked encoding iftrue. The default isfalse for compatibility reasons.
val head :(?headers:Http.Header.t->Uri.t->Http.Response.tio)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_contextval set_cache :Cohttp_lwt.S.call-> unitProvide a function used to process requests. Please seecall. The provided function is only used when noctx 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.tLwt.tuseCohttp_lwt.Connection instead.
val custom_ctx :?ctx:Conduit_lwt_unix.ctx->?resolver:Resolver_lwt.t->unit->Net.ctxcustom_ctx ?ctx ?resolver () will return a context that is the same as thedefault_ctx, but with either the connection handling or resolution module overridden withctx orresolver respectively. This is useful to supply aConduit_lwt_unix.ctx with a custom source network interface, or aResolver_lwt.t with a different name resolution strategy (for instance to override a hostname to point it to a Unix domain socket).