Option = {continue, boolean()} | {length, non_neg_integer()} | {read_length, non_neg_integer()} | {read_timeout, timeout()} | {transfer_decode, transfer_decode_fun(), any()} | {content_decode, content_decode_fun()}
cowboy_req - HTTP request and response
The cowboy_req
module provides functions to access, manipulate
and respond to requests.
The functions in this module follow patterns for their return types, based on the kind of function.
access: Value
action: ok | {Result, Req} | {Result, Value, Req}
modification: Req
question: boolean()
Whenever Req
is returned, you must use this returned value and
ignore any previous you may have had. This value contains various
values which are necessary for Cowboy to keep track of the request
and response states.
All functions which perform an action should only be called once. This includes reading the request body or replying. Cowboy will throw an error on the second call when it detects suspicious behavior.
It is highly discouraged to pass the Req object to another process.
Doing so and calling cowboy_req
functions from it leads to
undefined behavior.
Option = {continue, boolean()} | {length, non_neg_integer()} | {read_length, non_neg_integer()} | {read_timeout, timeout()} | {transfer_decode, transfer_decode_fun(), any()} | {content_decode, content_decode_fun()}
Request body reading options.
Option = {max_age, non_neg_integer()} | {domain, binary()} | {path, binary()} | {secure, boolean()} | {http_only, boolean()}
Cookie options.
The Req object.
All functions in this module receive a Req
as argument,
and some of them return a new object labelled Req2
in
the function descriptions below.
Alias of cowboy_req:binding/3
.
Binding name.
Default value.
Binding value.
Return the value for the given binding.
By default the value is a binary, however constraints may change the type of this value (for example automatically converting numbers to integer).
Binding name.
Binding value.
Return all bindings.
By default the value is a binary, however constraints may change the type of this value (for example automatically converting numbers to integer).
Alias of cowboy_req:header/3
.
Request header name.
Default value.
Request header value.
Return the value for the given header.
While header names are case insensitive, this function expects the name to be a lowercase binary.
Request headers.
Return all headers.
Requested host.
Return the requested host.
Extra tokens for the host.
Return the extra tokens from matching against ...
during routing.
Requested URL, without the path component.
Return the requested URL excluding the path component.
This function will always return undefined
until the
cowboy_router
middleware has been executed.
Cookie fields match rules.
Cookie fields matched.
Match cookies against the given fields.
Cowboy will only return the cookie values specified in the fields list, and ignore all others. Fields can be either the name of the cookie requested; the name along with a list of constraints; or the name, a list of constraints and a default value in case the cookie is missing.
This function will crash if the cookie is missing and no default value is provided. This function will also crash if a constraint fails.
The name of the cookie must be provided as an atom. The key of the returned map will be that atom. The value may be converted through the use of constraints, making this function able to extract, validate and convert values all in one step.
Query string fields match rules.
Query string fields matched.
Match the query string against the given fields.
Cowboy will only return the query string values specified in the fields list, and ignore all others. Fields can be either the key requested; the key along with a list of constraints; or the key, a list of constraints and a default value in case the key is missing.
This function will crash if the key is missing and no default value is provided. This function will also crash if a constraint fails.
The key must be provided as an atom. The key of the returned map will be that atom. The value may be converted through the use of constraints, making this function able to extract, validate and convert values all in one step.
Alias for cowboy_req:meta/3
.
Metadata name.
Default value.
Metadata value.
Return metadata about the request.
Request method.
Return the method.
Methods are case sensitive. Standard methods are always uppercase.
Cookie name.
Cookie value.
Parse and return all cookies.
Cookie names are case sensitive.
Alias of cowboy_req:parse_header/3
.
The parse_header/2
function will call parser_header/3
with a
different default value depending on the header being parsed. The
following table summarizes the default values used.
Header name | Header value |
---|---|
content-length |
|
cookie |
|
transfer-encoding |
|
Any other header |
|
Request header name.
Default value.
Parsed request header value.
Parse the given header.
While header names are case insensitive, this function expects the name to be a lowercase binary.
The parsed value differs depending on the header being parsed. The following table summarizes the different types returned.
Header name | Type of parsed header value |
---|---|
accept |
|
accept-charset |
|
accept-encoding |
|
accept-language |
|
authorization |
|
content-length |
|
content-type |
|
cookie |
|
expect |
|
if-match |
|
if-modified-since |
|
if-none-match |
|
if-unmodified-since |
|
range |
|
sec-websocket-protocol |
|
transfer-encoding |
|
upgrade |
|
x-forwarded-for |
|
Types for the above table:
Type = SubType = Charset = Encoding = LanguageTag = binary()
AuthType = Expect = OpaqueTag = Unit = binary()
Params = ContentTypeParams = [{binary(), binary()}]
Quality = 0..1000
AcceptExt = [{binary(), binary()} | binary()]
Credentials - see below
Range = {non_neg_integer(), non_neg_integer() | infinity} | neg_integer()
The cookie names and values, the values of the sec-websocket-protocol
and x-forwarded-for headers, the values in AcceptExt
and Params
,
the authorization Credentials
, the ExpectValue
and OpaqueTag
are case sensitive. All values in ContentTypeParams
are case sensitive
except the value of the charset parameter, which is case insensitive.
All other values are case insensitive and will be returned as lowercase.
The headers accept, accept-encoding and cookie headers can return an empty list. Some other headers are expected to have a value if provided and may crash if the value is missing.
The authorization header parsing code currently only supports basic
HTTP authentication. The Credentials
type is thus {Username, Password}
with Username
and Password
being binary()
.
The range header value Range
can take three forms:
{From, To}
: from From
to To
units
{From, infinity}
: everything after From
units
-Final
: the final Final
units
An undefined
tuple will be returned if Cowboy doesn’t know how
to parse the requested header.
Query string field name.
Query string field value.
Return the request’s query string as a list of tuples.
The atom true
is returned for keys which have no value.
Keys with no value are different from keys with an empty
value in that they do not have a =
indicating the presence
of a value.
Requested path.
Return the requested path.
Extra tokens for the path.
Return the extra tokens from matching against ...
during routing.
{inet:ip_address(), inet:port_number()}
Peer IP address and port number.
Return the client’s IP address and port number.
Requested port number.
Return the request’s port.
The port returned by this function is obtained by parsing the host header. It may be different than the actual port the client used to connect to the Cowboy server.
Unprocessed query string.
Return the request’s query string.
Metadata name.
Metadata value.
Set metadata about the request.
An existing value will be overwritten.
Requested URL.
Return the requested URL.
This function will always return undefined
until the
cowboy_router
middleware has been executed.
Client’s advertised HTTP version.
Return the HTTP version used for this request.
Alias of cowboy_req:body/2
.
Request body reading options.
Data read from the body.
Read the request body.
This function will read a chunk of the request body. If there is
more data to be read after this function call, then a more
tuple
is returned. Otherwise an ok
tuple is returned.
Cowboy will automatically send a 100 Continue
reply if
required. If this behavior is not desirable, it can be disabled
by setting the continue
option to false
.
Cowboy will by default attempt to read up to 8MB of the body,
but in chunks of 1MB. It will use a timeout of 15s per chunk.
All these values can be changed using the length
, read_length
and read_timeout
options respectively. Note that the size
of the data may not be the same as requested as the decoding
functions may grow or shrink it, and Cowboy makes not attempt
at returning an exact amount.
Cowboy will properly handle chunked transfer-encoding by
default. If any other transfer-encoding or content-encoding
has been used for the request, custom decoding functions
can be used. The content_decode
and transfer_decode
options allow setting the decode functions manually.
After the body has been streamed fully, Cowboy will remove the transfer-encoding header from the Req object, and add the content-length header if it wasn’t already there.
This function can only be called once. Cowboy will not cache the result of this call.
Length of the request body.
Return the length of the request body.
The length will only be returned if the request does not use any transfer-encoding and if the content-length header is present.
Alias of cowboy_req:body_qs/2
.
Request body reading options.
Field name.
Field value.
Return the request body as a list of tuples.
This function will parse the body assuming the content-type application/x-www-form-urlencoded, commonly used for the query string.
This function calls body/2
for reading the body, with the
same options it received. By default it will attempt to read
a body of 64KB in one chunk, with a timeout of 5s. If the
body is larger then a badlength
tuple is returned.
This function can only be called once. Cowboy will not cache the result of this call.
Return whether the request has a body.
Alias of cowboy_req:part/2
.
Request body reading options.
Part’s headers.
Read the headers for the next part of the multipart message.
Cowboy will skip any data remaining until the beginning of the next part. This includes the preamble to the multipart message but also the body of a previous part if it hasn’t been read. Both are skipped automatically when calling this function.
The headers returned are MIME headers, NOT HTTP headers.
They can be parsed using the functions from the cow_multipart
module. In addition, the cow_multipart:form_data/1
function
can be used to quickly figure out multipart/form-data
messages.
It takes the list of headers and returns whether this part is
a simple form field or a file being uploaded.
Note that once a part has been read, or skipped, it cannot be read again.
This function calls body/2
for reading the body, with the
same options it received. By default it will only read chunks
of 64KB with a timeout of 5s. This is tailored for reading
part headers, not for skipping the previous part’s body.
You might want to consider skipping large parts manually.
Alias of cowboy_req:part_body/2
.
Request body reading options.
Part’s body.
Read the body of the current part of the multipart message.
This function calls body/2
for reading the body, with the
same options it received. It uses the same defaults.
If there are more data to be read from the socket for this
part, the function will return what it could read inside a
more
tuple. Otherwise, it will return an ok
tuple.
Calling this function again after receiving a more
tuple
will return another chunk of body. The last chunk will be
returned inside an ok
tuple.
Note that once the body has been read, fully or partially, it cannot be read again.
Chunk data to be sent.
Send a chunk of data.
This function should be called as many times as needed
to send data chunks after calling chunked_reply/{2,3}
.
When the method is HEAD, no data will actually be sent.
If the request uses HTTP/1.0, the data is sent directly without wrapping it in an HTTP/1.1 chunk, providing compatibility with older clients.
Alias of cowboy_req:chunked_reply/3
.
Response status code.
Response headers.
Send a response using chunked transfer-encoding.
This function effectively sends the response status line and headers to the client.
This function will not send any body set previously. After
this call the handler must use the chunk/2
function
repeatedly to send the body in as many chunks as needed.
If the request uses HTTP/1.0, the data is sent directly without wrapping it in an HTTP/1.1 chunk, providing compatibility with older clients.
This function can only be called once, with the exception
of overriding the response in the onresponse
hook.
Send a 100 Continue intermediate reply.
This reply is required before the client starts sending the
body when the request contains the expect
header with the
100-continue
value.
Cowboy will send this automatically when required. However
you may want to do it manually by disabling this behavior
with the continue
body option and then calling this
function.
Response header name.
Delete the given response header.
While header names are case insensitive, this function expects the name to be a lowercase binary.
Return whether a response body has been set.
This function will return false if a response body has been set with a length of 0.
Response header name.
Return whether the given response header has been set.
While header names are case insensitive, this function expects the name to be a lowercase binary.
Alias of cowboy_req:reply/3
.
Alias of cowboy_req:reply/4
, with caveats.
Response status code.
Response headers.
Response body.
Send a response.
This function effectively sends the response status line, headers and body to the client, in a single send function call.
The reply/2
and reply/3
functions will send the body
set previously, if any. The reply/4
function overrides
any body set previously and sends Body
instead.
If a body function was set, and reply/2
or reply/3
was
used, it will be called before returning.
No more data can be sent to the client after this function returns.
This function can only be called once, with the exception
of overriding the response in the onresponse
hook.
Response body.
Set a response body.
This body will not be sent if chunked_reply/{2,3}
or
reply/4
is used, as they override it.
Alias of cowboy_req:set_resp_body_fun/3
.
Fun that will send the response body.
Socket for this connection.
Transport module for this socket.
Length of the response body.
Set a fun for sending the response body.
If a Length
is provided, it will be sent in the
content-length header in the response. It is recommended
to set the length if it can be known in advance. Otherwise,
the transfer-encoding header will be set to identity.
This function will only be called if the response is sent
using the reply/2
or reply/3
function.
The fun will receive the Ranch Socket
and Transport
as
arguments. Only send and sendfile operations are supported.
Fun that will send the response body.
Fun to call for every chunk to be sent.
Set a fun for sending the response body using chunked transfer-encoding.
This function will only be called if the response is sent
using the reply/2
or reply/3
function.
The fun will receive another fun as argument. This fun is to
be used to send chunks in a similar way to the chunk/2
function,
except the fun only takes one argument, the data to be sent in
the chunk.
Cookie name.
Cookie value.
Cookie options.
Set a cookie in the response.
Cookie names are case sensitive.
Response header name.
Response header value.
Set a response header.
You should use set_resp_cookie/4
instead of this function
to set cookies.