Page
Library
Module
Module type
Parameter
Class
Class type
Source
Opium.ResponseSourceModule to create and work with HTTP responses.
It offers convenience functions to create common responses and update them.
makeval make :
?version:Version.t ->
?status:Status.t ->
?reason:string ->
?headers:Headers.t ->
?body:Body.t ->
?env:Context.t ->
unit ->
tmake ?version ?status ?reason ?headers ?body ?env () creates a new response from the given values.
By default, the HTTP version will be set to 1.1, the HTTP status to 200 and the response will not contain any header or body.
of_plain_textval of_plain_text :
?version:Version.t ->
?status:Status.t ->
?reason:string ->
?headers:Headers.t ->
?env:Context.t ->
string ->
tof_plain_text ?status ?version ?reason ?headers ?env body creates a new response from the given values and a string body.
The content type of the response will be set to text/plain and the body will contain the string body.
Example
The response initialized with:
Response.of_plain_text "Hello World" Will be represented as:
HTTP/1.1 200 Content-Type: text/plain Hello World
of_jsonval of_json :
?version:Version.t ->
?status:Status.t ->
?reason:string ->
?headers:Headers.t ->
?env:Context.t ->
Yojson.Safe.t ->
tof_json ?status ?version ?reason ?headers ?env payload creates a new response from the given values and a JSON body.
The content type of the response will be set to application/json and the body will contain the json payload body.
Example
The response initialized with:
Response.of_json (`Assoc [ "Hello", `String "World" ]) Will be represented as:
HTTP/1.1 200
Content-Type: application/json
{"Hello":"World"} of_htmlval of_html :
?version:Version.t ->
?status:Status.t ->
?reason:string ->
?headers:Headers.t ->
?env:Context.t ->
?indent:bool ->
[ `Html ] Tyxml_html.elt ->
tof_html ?status ?version ?reason ?headers ?env ?indent payload creates a new response from the given values and a HTML body.
The content type of the response will be set to text/html; charset=utf-8 and the body will contain the HTML payload payload.
The header Connection will be set to Keep-Alive to opimize for bandwitdh, since it is assumed that users who response HTML content will be likely to make further responses.
Example
The response initialized with:
let my_page =
let open Tyxml.Html in
html (head (title (txt "Title")) []) (body [ h1 [ txt "Hello World!" ] ])
;;
let res = Response.of_html ~indent:true my_pageres will be represented as:
HTTP/1.1 200 Connection: Keep-Alive Content-Type: text/html; charset=utf-8 <!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"><head><title>Title</title></head> <body><h1>Hello World!</h1></body> </html>
of_xmlval of_xml :
?version:Version.t ->
?status:Status.t ->
?reason:string ->
?headers:Headers.t ->
?env:Context.t ->
?indent:bool ->
Tyxml_xml.elt ->
tof_xml ?status ?version ?reason ?headers ?env ?indent payload creates a new response from the given values and a XML body.
The content type of the response will be set to text/xml; charset=utf-8 and the body will contain the XML payload payload.
Example
The response initialized with:
let xml =
let open Tyxml.Xml in
node
"note"
[ node "to" [ pcdata "Tove" ]
; node "from" [ pcdata "Jani" ]
; node "heading" [ pcdata "Reminder" ]
; node "body" [ pcdata "Don't forget me this weekend!" ]
]
;;
let res = Response.of_xml ~indent:true xmlres will be represented as:
HTTP/1.1 200 Content-Type: application/xml charset=utf-8 <note><to>Tove</to><from>Jani</from><heading>Reminder</heading> <body>Don't forget me this weekend!</body> </note>
of_svgval of_svg :
?version:Version.t ->
?status:Status.t ->
?reason:string ->
?headers:Headers.t ->
?env:Context.t ->
?indent:bool ->
[ `Svg ] Tyxml_svg.elt ->
tof_svg ?status ?version ?reason ?headers ?env ?indent payload creates a new response from the given values and a SVG body.
The content type of the response will be set to image/svg+xml and the body will contain the SVG payload payload.
The header Connection will be set to Keep-Alive to opimize for bandwitdh, since it is assumed that users who response SVG content will be likely to make further responses.
Example
The response initialized with:
let my_svg =
let open Tyxml.Svg in
svg
[ circle
~a:
[ a_cx (50., None)
; a_cy (50., None)
; a_r (40., None)
; a_fill (`Color ("black", None))
]
[]
]
;;
let res = Response.of_svg ~indent:true my_svgres will be represented as:
HTTP/1.1 200 Connection: Keep-Alive Content-Type: image/svg+xml <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"> <circle cx="50" cy="50" r="40" fill="black"></circle> </svg>
redirect_toval redirect_to :
?status:Status.redirection ->
?version:Version.t ->
?reason:string ->
?headers:Headers.t ->
?env:Context.t ->
string ->
tredirect_to ?status ?version ?reason ?headers ?env target creates a new Redirect response from the given values.
The response will contain the header Location with the value target and a Redirect HTTP status (a Redirect HTTP status starts with 3).
By default, the HTTP status is 302 Found.
The response initialized with:
Response.redirect_to "/redirected" Will be represented as:
HTTP/1.1 302 Location: /redirected
to_jsonto_json t parses the body of the response t as a JSON structure.
If the body of the response cannot be parsed as a JSON structure, None is returned. Use to_json_exn to raise an exception instead.
Example
let response = Response.of_json (`Assoc [ "Hello", `String "World" ])
let body = Response.to_json responsebody will be:
`Assoc [ "Hello", `String "World" ] to_json_exnto_json_exn t parses the body of the response t as a JSON structure.
If the body of the response cannot be parsed as a JSON structure, an Invalid_argument exception is raised. Use to_json to return an option instead.
to_plain_textto_plain_text t parses the body of the response t as a string.
Example
let response = Response.of_plain_text "Hello world!"
let body = Response.to_json responsebody will be:
"Hello world!" statusset_statusset_status status response returns a copy of response with the HTTP status set to content_type.
header key t returns the value of the header with key key in the response t.
If multiple headers have the key key, only the value of the first header will be returned.
If you want to return all the values if multiple headers are found, you can use headers.
headersheaders returns the values of all headers with the key key in the response t.
If you want to return the value of only the first header with the key key, you can use header.
add_headeradd_header (key, value) t adds a header with the key key and the value value to the response t.
If a header with the same key is already persent, a new header is appended to the list of headers regardless. If you want to add the header only if an header with the same key could not be found, you can use add_header_unless_exists.
See also add_headers to add multiple headers.
add_header_or_replaceadd_header_or_replace (key, value) t adds a header with the key key and the value value to the response t.
If a header with the same key already exist, its value is replaced by value. If you want to add the header only if it doesn't already exist, you can use add_header_unless_exists.
See also add_headers_or_replace to add multiple headers.
add_header_unless_existsadd_header_unless_exists (key, value) t adds a header with the key key and the value value to the response t if an header with the same key does not already exist.
If a header with the same key already exist, the response remains unmodified. If you want to add the header regardless of whether the header is already present, you can use add_header.
See also add_headers_unless_exists to add multiple headers.
add_headersadd_headers headers response adds the headers headers to the response t.
The headers are added regardless of whether a header with the same key is already present. If you want to add the header only if an header with the same key could not be found, you can use add_headers_unless_exists.
See also add_header to add a single header.
add_headers_or_replaceadd_headers_or_replace (key, value) t adds a headers headers to the response t.
If a header with the same key already exist, its value is replaced by value. If you want to add the header only if it doesn't already exist, you can use add_headers_unless_exists.
See also add_header_or_replace to add a single header.
add_headers_unless_existsadd_headers_unless_exists headers response adds the headers headers to the response t if an header with the same key does not already exist.
If a header with the same key already exist, the header is will not be added to the response. If you want to add the header regardless of whether the header is already present, you can use add_headers.
See also add_header_unless_exists to add a single header.
remove_headerremove_header (key, value) t removes all the headers with the key key from the response t.
If no header with the key key exist, the response remains unmodified.
content_typecontent_type response returns the value of the header Content-Type of the response response.
set_content_typeset_content_type content_type response returns a copy of response with the value of the header Content-Type set to content_type.
etagetag response returns the value of the header ETag of the response response.
set_etagset_etag etag response returns a copy of response with the value of the header ETag set to etag.
locationlocation response returns the value of the header Location of the response response.
set_locationset_location location response returns a copy of response with the value of the header Location set to location.
cache_controlcache_control response returns the value of the header Cache-Control of the response response.
set_cache_controlset_cache_control cache_control response returns a copy of response with the value of the header Cache-Control set to cache_control.
cookiecookie ?signed_with key t returns the value of the cookie with key key in the Set-Cookie header of the response t.
If signed_with is provided, the cookies will be unsigned with the given Signer and only a cookie with a valid signature will be returned.
If the response does not contain a valid Set-Cookie or if no cookie with the key key exist, None will be returned.
cookiescookies ?signed_with t returns all the value of the cookies in the Set-Cookie header of the response t.
If signed_with is provided, the cookies will be unsigned with the given Signer and only the cookies with a valid signature will be returned.
If the response does not contain a valid Set-Cookie, None will be returned.
add_cookieval add_cookie :
?sign_with:Cookie.Signer.t ->
?expires:Cookie.expires ->
?scope:Uri.t ->
?same_site:Cookie.same_site ->
?secure:bool ->
?http_only:bool ->
Cookie.value ->
t ->
tadd_cookie ?sign_with ?expires ?scope ?same_site ?secure ?http_only value t adds a cookie with value value to the response t.
If a cookie with the same key already exists, its value will be replaced with the new value of value.
If sign_with is provided, the cookie will be signed with the given Signer.
add_cookie_or_replaceval add_cookie_or_replace :
?sign_with:Cookie.Signer.t ->
?expires:Cookie.expires ->
?scope:Uri.t ->
?same_site:Cookie.same_site ->
?secure:bool ->
?http_only:bool ->
Cookie.value ->
t ->
tadd_cookie_or_replace ?sign_with ?expires ?scope ?same_site ?secure ?http_only value t adds a cookie with value value to the response t. If a cookie with the same key already exists, its value will be replaced with the new value of value. If sign_with is provided, the cookie will be signed with the given Signer.
add_cookie_unless_existsval add_cookie_unless_exists :
?sign_with:Cookie.Signer.t ->
?expires:Cookie.expires ->
?scope:Uri.t ->
?same_site:Cookie.same_site ->
?secure:bool ->
?http_only:bool ->
Cookie.value ->
t ->
tadd_cookie_unless_exists ?sign_with ?expires ?scope ?same_site ?secure ?http_only value t adds a cookie with value value to the response t.
If a cookie with the same key already exists, it will remain untouched.
If sign_with is provided, the cookie will be signed with the given Signer.
remove_cookieremove_cookie key t removes the cookie of key key from the Set-Cookie header of the response t.
sexp_of_tpppp formats the response t as an s-expression
pp_humpp_hum formats the response t as a standard HTTP response