Package io.ktor.server.response
Types
A server's response. To learn how to send responses inside route handlers, see Sending responses.
Server response send pipeline.
An HTTP/2 push builder.
Server's response cookies.
Server's response headers.
An HTTP/2 push builder interface.
HTTP/2 push is no longer supported by the Chrome web browser. Other browsers may discard it at some point. With such browsers, HTTP/2 push will be disabled, therefore using this plugin is safe, but it will have no effect. On the other hand, this plugin is not deprecated and generally it is still allowed to use it, so feel free to opt in this annotation to eliminate this warning, if you are sure that you need it. For example, it makes sense to use with a non-browser client that for sure supports HTTP/2 push.
Functions
Appends the Cache-Control
header with the specified value to a response.
Appends the Content-Range
header with the specified range and fullLength to a response.
Creates a default ContentType based on the given contentType and current call.
Appends the E-Tag
header with the specified value to a response.
Append HTTP response header with temporal date (date, time and so on)
Responds to a client with a raw bytes response, using the specified provider to build a byte array.
Responds to a client with a raw bytes response, using specified bytes.
Respond with a binary content producer.
Responds to a client with a contents of a file
Respond with binary content producer.
Responds to a client with a 301 Moved Permanently
or 302 Found
redirect. Unlike the other respondRedirect, it provides a way to build a URL based on current call using the block function.
Responds to a client with a 301 Moved Permanently
or 302 Found
redirect.
Responds to a client with a plain text response, using the specified provider to build a text.
Responds to a client with a plain text response.
Respond with text content writer.
Properties
A type of response object that is passed in the respond function. Can be useful for custom serializations.