Basic security handler
Security handler that adds basic access authentication to the wrapped handler.
A very basic security handler implementation that uses basic access authentication and checks against a static (in-memory) list of user credentials. Does not use any security constraints or user roles; any access to the handler it wraps simply requires one of the configured usernames and passwords.
Credentials
Comma-separated list of valid credentials for accessing the wrapped handler. Credentials must be written as a username & password pair with a colon (:) separating them. For example: user1:PuYcRK92, user2:YpYp7gPe
For flexibility, consider using a ${placeholder}
value.
Required
Wrapped handler type
Specifies wrapped handler type.
Resource Handler Looks for a matching file in the local directory to serve. If a file is not found, then the request is passed to the default handler which generates a 404 (or favicon.ico).
Servlet Handler Generates content by passing the request to a Servlet mapped by a URI pattern.
The resource handler is passed the request first and looks for a matching file in the local directory to serve. If a file is not found, then the request is passed to the default handler which generates a 404 (or favicon.ico).
Resource base
Specifies where to look for the matching files.
Directories listed
If set, a listing of the content of a directory is returned when that directory inside the base directory matches the received request.
Aliases
Set if resource aliases (eg symlink, 8.3 names, case insensitivity) are allowed.
Allowing aliases can significantly increase security vulnerabilities.
The ServletHandler generates content by passing the request to a Servlet mapped by a URI pattern.
First, the URI is matched against the mapping. The mapping maps URI's to servlet names. Second, the servlet(s) with the mapped names are resolved from the servlet list. This servlet(s) handles the received request.
Note: This handler is intended to be used when a full web application is not required. Specifically filters and request wrapping are not supported.
Servlets
Servlets receive and respond to requests from Web clients, usually across HTTP, the HyperText Transfer Protocol.
Simple dispatcher servlet Delegates all request handling to the specified Spring Web MVC Controller. This controller uses the view resolver to create a reply message.
Web service message receiver servlet Delegates all request handling to the specified Spring Web Services WebServiceMessageReceiver.
Servlet mappings
Mapping from specific paths to servlet names.
Servlets with these names should be specified.