Jetty Server
Jetty HTTP Servlet Server.
This server aggregates Connectors (HTTP request receivers) and request Handlers.
Connectors
Set the HTTP Connectors that use this server to handle HTTP requests.
A connector receives requests (normally from a socket) and calls the handle method of this server to handle this requests.
Use a Select Channel Connector when there are many connections that have idle periods. Use a Blocking channel selector when there are a few very active connections.
Handler type
Responsible for handling incoming HTTP requests and sending the corresponding response.
1. Coordinating Handlers 1.1 Handler List List of handlers which are called in turn until either an exception is thrown, the response is committed or a positive response status is set. 1.2 Context Handler Collection Collection of Context Handlers of which some are selected by best match for the context path. Multiple contexts may have the same context path and they are called in order until one handles the request.
2. Filtering Handlers 2.1 Context Handler Group another handler below a particular URI context path 2.2 Servlet Context Handler Extension to the Context Handler allows for simple construction of a context with a Servlet Handler 2.3 Basic Security Handler Adds basic access authentication to the handler it wraps.
3. Generating Handlers 3.1 Resource Handler Looks for a matching file in the local directory to serve. 3.2 Servlet Handler Generates content by passing the request to a Servlet mapped by a URI pattern. Intended to be used when a full web application is not required. Specifically filters and request wrapping are not supported.
Graceful shutdown
Set graceful shutdown timeout.
If set, shutting down the server will not immediately stop the server. Instead, all Connectors will be closed so that new connections will not be accepted and all contexthandlers will be put into the shutdown mode so that no new requests will be accepted, but existing requests can complete.
The server will then wait the configured timeout before stopping.
Send date header
Wether to include the Date
HTTP header in all responses.
Default is false
.
Send server version
Wether to include the Server
HTTP header in all responses.
Default is false
.
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.
Generates content by passing the request to a Servlet mapped by a URI pattern. Intended to be used when a full web application is not required. Specifically filters and request wrapping are not supported.
Context handler that groups a Servlet handler below a particular URI context path
Context path
Defines which requests are handled by this handler.
eg: /myapp
List of handlers which are called in turn until either an exception is thrown, the response is committed or a positive response status is set.
Context Handler Group another handler below a particular URI context path Servlet Context Handler Extension to the Context Handler allows for simple construction of a context with a Servlet Handler
Resource Handler Looks for a matching file in the local directory to serve. Servlet Handler Generates content by passing the request to a Servlet mapped by a URI pattern. Intended to be used when a full web application is not required. Specifically filters and request wrapping are not supported.
Collection of Context Handlers of which some are selected by best match for the context path. Multiple contexts may have the same context path and they are called in order until one handles the request.
Context Handler Group another handler below a particular URI context path Servlet Context Handler Extension to the Context Handler allows for simple construction of a context with a Servlet Handler
Resource Handler Looks for a matching file in the local directory to serve. Servlet Handler Generates content by passing the request to a Servlet mapped by a URI pattern. Intended to be used when a full web application is not required. Specifically filters and request wrapping are not supported.
A ContextHandler is a HandlerWrapper that responds only to requests that have a URI prefix that matches the configured context path.
Context path
Defines which requests are handled by this handler.
eg: /myapp
Wrapped handler type
Specifies wrapped handler type.
1. 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). 2. 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.
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.
Id
Name that uniquely identifies this flow component.
Required
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.
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.
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.
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.