Set whether the router should parse "forwarded"-type headers
Remove all the routes from this router
Add a route that matches a HTTP CONNECT request and the specified path regex
Add a route that matches a HTTP DELETE request and the specified path regex
Specify an handler to handle an error for a particular status code. You can use to manage general errors too using status code 500. The handler will be called when the context fails and other failure handlers didn't write the reply or when an exception is thrown inside an handler. You must not use {@link RoutingContext#next} inside the error handler This does not affect the normal failure routing logic.
Get some data from metadata.
Add a route that matches a HTTP GET request and the specified path regex
Used to route a context to the router. Used for sub-routers. You wouldn't normally call this method directly.
Used to route a failure to the router. Used for sub-routers. You wouldn't normally call this method directly.
Add a route that matches a HTTP HEAD request and the specified path regex
Add a route that matches a HTTP OPTIONS request and the specified path regex
Add a route that matches a HTTP PATCH request and the specified path regex
Add a route that matches a HTTP POST request and the specified path regex
Put metadata to this router. Used for saved extra data. Remove the existing value if value is null.
Add a route that matches a HTTP PUT request and the specified path regex
Add a route that matches a HTTP TRACE request and the specified path regex
Create a router
Generated using TypeDoc
A router receives request from an {@link HttpServer} and routes it to the first matching Route that it contains. A router can contain many routes.
Routers are also used for routing failures.