package cohttp-mirage
Legend:
Library
Module
Module type
Parameter
Class
Class type
Library
Module
Module type
Parameter
Class
Class type
module IO : Cohttp_lwt.S.IO
include Cohttp.Generic.Server.S
with type body = Cohttp_lwt.Body.t
and module IO := IO
type body = Cohttp_lwt.Body.t
type conn = IO.conn * Cohttp.Connection.t
A request handler can respond in two ways:
- Using
`Response
, with aResponse.t
and abody
. - Using
`Expert
, with aResponse.t
and an IO function that is expected to write the response body. The IO function has access to the underlyingIO.ic
andIO.oc
, which allows writing a response body more efficiently, stream a response or to switch protocols entirely (e.g. websockets). Processing of pipelined requests continue after theunitIO.t
is resolved. The connection can be closed by closing theIO.ic
.
val respond :
?headers:Http.Header.t ->
?flush:bool ->
status:Http.Status.t ->
body:body ->
unit ->
(Http.Response.t * body) IO.t
respond ?headers ?flush ~status ~body
will respond to an HTTP request with the given status
code and response body
. If flush
is true, then every response chunk will be flushed to the network rather than being buffered. flush
is true by default. The transfer encoding will be detected from the body
value and set to chunked encoding if it cannot be determined immediately. You can override the encoding by supplying an appropriate Content-length
or Transfer-encoding
in the headers
parameter.
Resolve a URI and a docroot into a concrete local filename.
val respond_need_auth :
?headers:Http.Header.t ->
auth:Cohttp.Auth.challenge ->
unit ->
(Http.Response.t * body) IO.t
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>