This class handles all functionality involved in crafting a http response.
Much of the functionality is inspired by the Request class in Express.js, so
the documentation for this will
complement this document. As reqres is build on top of the
Rook specifications
the Response object can be converted to a compliant list object to be
passed on to e.g. the httpuv handler. A Response object is always created
as a response to a Request object and contains a reference to the
originating Request object. A Response is always initialized with a
404 Not Found code, an empty string as body and the Content-Type header set
to text/plain. As the Content-Type header is required for httpuv to
function, it will be inferred if missing when converting to a list. If the
body is a raw vector it will be set to application/octet-stream and
otherwise it will be set to text/plain. It is always advised to consciously
set the Content-Type header though. The only exception is when attaching a
standard file where the type is inferred from the file extension
automatically. Unless the body is a raw vector it will automatically be
converted to a character vector and collapsed to a single string with "\n"
separating the individual elements before the Response object is converted
to a list (that is, the body can exist as any type of object up until the
moment where the Response object is converted to a list). To facilitate
communication between different middleware the Response object contains
a data store where information can be stored during the lifetime of the
response.
Usage
# S3 method for class 'Response'
as.list(x, ...)
is.Response(x)Value
A rook-compliant list-response (in case of as.list()) or a logical
indicating whether the object is a Response (in case of is.Response())
Initialization
A new 'Response'-object is initialized using the new() method on the
generator:
Usage
res <- Response$new(request) |
But often it will be provided by the request using the respond() method,
which will provide the response, creating one if it doesn't exist
Usage
res <- request$respond() |
Arguments
request | The Request object that the Response is responding to |
Fields
The following fields are accessible in a Response object:
statusGets or sets the status code of the response. Is initialised with
404LbodySet or get he body of the response. If it is a character vector with a single element named
'file'it will be interpreted as the location of a file. It is better to use thefilefield for creating a response referencing a file as it will automatically set the correct headers.fileSet or get the location of a file that should be used as the body of the response. If the body is not referencing a file (but contains something else) it will return
NULL. TheContent-Typeheader will automatically be inferred from the file extension, if known. If unknown it will defaults toapplication/octet-stream. If the file has no extension it will betext/plain. Existence of the file will be checked.typeGet or sets the
Content-Typeheader of the response based on a file extension or mime-type.requestGet the original
Requestobject that the object is responding to.
See also
Request for handling http requests
Active bindings
statusGets or sets the status code of the response. Is initialised with
404LbodySet or get he body of the response. If it is a character vector with a single element named
'file'it will be interpreted as the location of a file. It is better to use thefilefield for creating a response referencing a file as it will automatically set the correct headers.fileSet or get the location of a file that should be used as the body of the response. If the body is not referencing a file (but contains something else) it will return
NULL. TheContent-Typeheader will automatically be inferred from the file extension, if known. If unknown it will defaults toapplication/octet-stream. If the file has no extension it will betext/plain. Existence of the file will be checked.typeGet or sets the
Content-Typeheader of the response based on a file extension or mime-type.requestGet the original
Requestobject that the object is responding to.formatterGet the registered formatter for the response body.
is_formattedHas the body been formatted
Methods
Method set_header()
Sets the header given by name. value will be converted
to character. A header will be added for each element in value. Use
append_header() for setting headers without overwriting existing ones.
Method append_header()
Adds an additional header given by name with the value
given by value. If the header does not exist yet it will be created.
Method attach()
Sets the body to the file given by file and marks the
response as a download by setting the Content-Disposition to
attachment; filename=<filename>. Use the type argument to overwrite
the automatic type inference from the file extension.
Usage
Response$attach(file, filename = basename(file), type = NULL)Method as_download()
Marks the response as a downloadable file, rather than data to be shown in the browser
Method status_with_text()
Sets the status to code and sets the body to the
associated status code description (e.g. Bad Gateway for 502L)
Method set_cookie()
Sets a cookie on the response. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie for a longer description
Usage
Response$set_cookie(
name,
value,
encode = TRUE,
expires = NULL,
http_only = NULL,
max_age = NULL,
path = NULL,
secure = NULL,
same_site = NULL
)Arguments
nameThe name of the cookie
valueThe value of the cookie
encodeShould
valuebe url encodedexpiresA POSIXct object given the expiration time of the cookie
http_onlyShould the cookie only be readable by the browser
max_ageThe number of seconds to elapse before the cookie expires
pathThe URL path this cookie is related to
secureShould the cookie only be send over https
same_siteEither
"Lax"or"Strict"indicating whether the cookie can be send during cross-site requests
Method set_links()
Sets the Link header based on the named arguments passed
to .... The names will be used for the rel directive.
Method format()
Based on the formatters passed in through ... content
negotiation is performed with the request and the preferred formatter is
chosen and applied. The Content-Type header is set automatically. If
compress = TRUE the compress() method will be called after formatting.
If an error is encountered and autofail = TRUE the response will be set
to 500. If a formatter is not found and autofail = TRUE the response
will be set to 406. If formatting is successful it will return TRUE,
if not it will return FALSE
Method set_formatter()
Based on the formatters passed in through ... content
negotiation is performed with the request and the preferred formatter is
chosen. The Content-Type header is set automatically. If a formatter is
not found and autofail = TRUE the response will be set to 406. The
found formatter is registered with the response and will be applied just
before handing off the response to httpuv, unless the response has been
manually formatted.
Method compress()
Based on the provided priority, an encoding is negotiated
with the request and applied. The Content-Encoding header is set to the
chosen compression algorithm.
Usage
Response$compress(
priority = c("gzip", "deflate", "br", "identity"),
force = FALSE
)Method content_length()
Calculates the length (in bytes) of the body. This is the
number that goes into the Content-Length header. Note that the
Content-Length header is set automatically by httpuv so this method
should only be called if the response size is needed for other reasons.
Method as_list()
Converts the object to a list for further processing by
a Rook compliant server such as httpuv. Will set Content-Type header
if missing and convert a non-raw body to a single character string. Will
apply the formatter set by set_formatter() unless the body has already
been formatted. Will add a Date header if none exist.
Examples
fake_rook <- fiery::fake_request(
'http://example.com/test?id=34632&question=who+is+hadley',
content = 'This is elaborate ruse',
headers = list(
Accept = 'application/json; text/*',
Content_Type = 'text/plain'
)
)
req <- Request$new(fake_rook)
res <- Response$new(req)
res
#> ── An HTTP response ────────────────────────────────────────────────────────────
#> Status: 404 - Not Found
#> Content type: text/plain
#> → Responding to: http://example.com:80/test?id=34632&question=who+is+hadley
# Set the body to the associated status text
res$status_with_text(200L)
res$body
#> [1] "OK"
# Infer Content-Type from file extension
res$type <- 'json'
res$type
#> [1] "application/json"
# Prepare a file for download
res$attach(system.file('DESCRIPTION', package = 'reqres'))
res$type
#> [1] "text/plain"
res$body
#> file
#> "/home/runner/work/_temp/Library/reqres/DESCRIPTION"
res$get_header('Content-Disposition')
#> [1] "attachment; filename=\"DESCRIPTION\""
# Cleaning up connections
rm(fake_rook, req, res)
gc()
#> used (Mb) gc trigger (Mb) max used (Mb)
#> Ncells 1145168 61.2 2194742 117.3 2194742 117.3
#> Vcells 2146571 16.4 8388608 64.0 3004359 23.0