Package-level declarations
Types
Evaluates a route as a result of the AND operation using two other selectors.
Evaluates a route against a constant query parameter value.
Evaluates a route against a request's host and port.
Evaluates a route against a Content-Type
in the HttpHeaders.Accept request header.
Evaluates a route against a header in the request.
Evaluates a route against an HttpMethod.
Evaluates a route against a Content-Type
in the HttpHeaders.Accept request header.
Evaluates a route against the port on which a call is received.
Evaluates a route against an optional query parameter value and captures its value, if found.
Evaluates a route as a result of the OR operation using two other selectors.
Evaluates a route against a query parameter value and captures its value.
Evaluates a route against a constant path segment.
Evaluates a route against an optional parameter path segment and captures its value, if any.
Evaluates a route against a parameter path segment and captures its value.
A helper object for building instances of RouteSelector from path segments.
Evaluates a route against any number of trailing path segments, and captures their values.
Evaluates a route against any single path segment.
A selector for a routing root.
Describes a node in a routing tree.
Serves as the base type for routing selectors.
A result of a route evaluation against a call.
A root routing node of an Application. You can learn more about routing in Ktor from Routing.
A single act of communication between a client and server that is handled in Routing.
The context of a RoutingHandler that is used to handle a RoutingCall.
A function that handles a RoutingCall.
A parsed routing path. Consist of number of segments parts.
A single routing path segment.
Possible routing path segment kinds.
An application call handled by Routing.
An application request handled by Routing.
An application response handled by Routing.
A client's request that can be handled in Routing. To learn how to handle incoming requests, see Handling requests.
Represents a context in which routing resolution is being performed
Represents a result of routing resolution.
Represents the trace of routing resolution process for diagnostics.
Represents a single entry in the RoutingResolveTrace.
A server's response that can be used to respond in Routing. To learn how to send responses inside route handlers, see Sending responses.
Evaluates a route against a single trailing slash.
Properties
Gets an Application for this RouteNode by scanning the hierarchy to the root.
A plugin that enables ignoring a trailing slash when resolving URLs.
Functions
Builds a route to match requests with the HttpHeaders.Accept header matching any of the specified contentTypes.
Builds a route to match requests with the HttpHeaders.ContentType header matching the specified contentType.
Creates a routing entry for the specified path.
Builds a route to match DELETE
requests.
Builds a route to match DELETE
requests with the specified path.
Builds a route to match DELETE
requests with the specified regex path. Named parameters from regex can be accessed via ApplicationCall.parameters.
Builds a route to match GET
requests.
Builds a route to match GET
requests with the specified path.
Builds a route to match GET
requests with the specified regex path. Named parameters from regex can be accessed via ApplicationCall.parameters.
Return list of endpoints with handlers under this route.
Builds a route to match HEAD
requests.
Builds a route to match HEAD
requests with the specified path.
Builds a route to match HEAD
requests with the specified regex path. Named parameters from regex can be accessed via ApplicationCall.parameters.
Creates a route to match a request's host and port. There are no any host resolutions/transformations applied to a host: a request host is treated as a string.
Creates a route to match a request host and port. There are no any host resolutions/transformations applied to a host: a request host is treated as a string.
Creates a route to match s request host and port. There are no any host resolutions/transformations applied to a host: a request host is treated as a string.
Builds a route to match OPTIONS
requests.
Builds a route to match OPTIONS
requests with the specified path.
Builds a route to match OPTIONS
requests with the specified regex path. Named parameters from regex can be accessed via ApplicationCall.parameters.
Builds a route to match PATCH
requests.
Builds a route to match PATCH
requests receiving a request body as content of the R type.
Builds a route to match PATCH
requests with the specified path.
Builds a route to match PATCH
requests with the specified path receiving a request body as content of the R type.
Builds a route to match PATCH
requests with the specified regex path. Named parameters from regex can be accessed via ApplicationCall.parameters.
Builds a route to match PATCH
requests with the specified regex path receiving a request body as content of the R type. Named parameters from regex can be accessed via ApplicationCall.parameters.
Builds a route to match POST
requests.
Builds a route to match POST
requests receiving a request body as content of the R type.
Builds a route to match POST
requests with the specified path.
Builds a route to match POST
requests with the specified path receiving a request body as content of the R type.
Builds a route to match POST
requests with the specified regex path. Named parameters from regex can be accessed via ApplicationCall.parameters.
Builds a route to match POST
requests with the specified regex path receiving a request body as content of the R type. Named parameters from regex can be accessed via ApplicationCall.parameters.
Builds a route to match PUT
requests.
Builds a route to match PUT
requests receiving a request body as content of the R type.
Builds a route to match PUT
requests with the specified path.
Builds a route to match PUT
requests with the specified path receiving a request body as content of the R type.
Builds a route to match PUT
requests with the specified regex path. Named parameters from regex can be accessed via ApplicationCall.parameters.
Builds a route to match PUT
requests with the specified regex path receiving a request body as content of the R type. Named parameters from regex can be accessed via ApplicationCall.parameters.
Builds a route to match the specified path.
Builds a route to match the specified regex path. Named parameters from regex can be accessed via ApplicationCall.parameters.
Builds a route to match the specified HTTP method and regex path. Named parameters from regex can be accessed via ApplicationCall.parameters.
Installs a Routing plugin for the this Application and runs a configuration script on it. You can learn more about routing in Ktor from Routing.