private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services for sponsored feature development
Table of Contents
Jetty ships with a bundle of servlets that interact with the key classes. Most are in the org.eclipse.jetty.servlets package. These servlets and filters are among the principle elements of Jetty as a component-based infrastructure that holds and runs J2EE applications. As described, they play a major role in running and maintaining the Jetty server.
Also included are a number of Jetty specific handlers that allow access to internals of jetty that would not normally be exposed and are very useful testing environments and many production scenarios.
DefaultServlet implements the
ResourceFactory interface and extends the
HttpServlet abstract class.
It is usually mapped to "/" and provides handling for static content,
TRACE methods for the context.
MOVE method is allowed if
DELETE are allowed.
Jetty supports the following
true, range requests and responses are supported.
true, directory listings are returned if no welcome file is found. Otherwise 403 Forbidden displays.
true, welcome files are redirected rather that forwarded.
true, attempt to dispatch to welcome files that are servlets, but only after no matching static resources could be found. If
false, then a welcome file must exist on disk. If
exact, then exact servlet matches are supported without an existing file. Default is
true. This must be
falseif you want directory listings, but have index.jsp in your welcome file list.
br=.br,gzip=.gz,bzip2=.bz. If set to a boolean
true, then a default set of compressed formats will be used, otherwise no precompressed formats supported.
precompressedinstead. If set to
true, then static content is served as gzip content encoded if a matching resource is found ending with ".gz".
true, only the path info will be applied to the resourceBase
true, weak etags will be generated and handled.
true, mapped file buffer serves static content. Setting this value to
falsemeans that a direct buffer is used instead of a mapped file buffer. By default, this is set to