All Classes and Interfaces
Class
Description
An authentication handler that provides API Key support.
Base interface for auth handlers.
Base interface for authorization handlers that provide authorization support.
An auth handler that provides HTTP Basic Authentication support.
A handler which gathers the entire request body and sets it on the .
Represents an event that occurs on the event bus bridge.
An auth handler that chains to a sequence of handlers.
A session store which stores sessions in a distributed map so they are available across the cluster.
A handler which implements server side http://www.w3.org/TR/cors/[CORS] support for Vert.x-Web.
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of
attacks, including Cross Site Scripting (XSS) and data injection attacks.
This handler adds a CSRF token to requests which mutate state.
An auth handler that provides HTTP Basic Authentication support.
A pretty error handler for rendering error pages.
A handler that serves favicons.
Represents a file-upload from an HTTP multipart form submission.
Handler that handles login from a form on a custom login page.
HTTP Strict Transport Security (HSTS) RFC6797.
Base input trust interface for handlers that verify the trust of the request.
An auth handler that provides JWT Authentication support.
A parsed language header.
A session store which is only available on a single node.
Implement to format the output of the
LoggerHandlerA handler which logs request information to the Vert.x logger.
NOTE: This class has been automatically generated from the
original non Mutiny-ified interface using Vert.x codegen.A handler which selectively executes another handler if a precondition is met.
An auth handler that provides OAuth2 Authentication support.
An auth handler that provides One Time Password (Multi-Factor) Authentication support.
A container with the request's headers that are meaningful enough to be parsed
Contains:
Accept -> MIME header, parameters and sortable
Accept-Charset -> Parameters and sortable
Accept-Encoding -> Parameters and sortable
Accept-Language -> Parameters and sortable
Content-Type -> MIME header and parameters
Base platform interface for handlers that provide functionality to the application platform.
Base interface for handlers that perform protocol upgrades.
An auth handler that's used to handle auth by redirecting user to a custom login page.
A handler which sets the response content type automatically according to the best
Accept header match.Handler which adds a header `x-response-time` in the response of matching requests containing the time taken
in ms to process the request.
A route is a holder for a set of criteria which determine whether an HTTP request or failure should be routed
to a handler.
A router receives request from an
HttpServer and routes it to the first matching
Route that it contains.Represents the context for the handling of a request in Vert.x-Web.
Base security policy interface for handlers that provide HTTP security related headers.
Represents a browser session.
A handler that maintains a
Session for each browser
session.A session store is used to store sessions for an Vert.x-Web web app
A user customizable authentication handler.
A handler that allows you to handle SockJS connections from clients.
You interact with SockJS clients through instances of SockJS socket.
A handler for serving static resources from the file system or classpath.
A handler which renders responses using a template engine and where the template name is selected from the URI
path.
Handler that will timeout requests if the response has not been written after a certain time.
An auth handler that provides FIDO2 WebAuthN Relay Party support.
The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render
a page in a