Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Jetty 6 ships with a bundle of servlets that interacts with the key classes. Mostly they can be found in the org.mortbay.servlet package. Here is a list of servlets playing a major role in running and maintaining the Jetty server:


 The CGI servlet class extends the abstract HttpServlet class. When the init parameter is called, the cge bin directory is set with the cgibinResourceBase otherwise, it will default to the resource base of the context. There are three parameteres that the cgi bin is using:


 commandPrefix - this is the init parameter that is obtained when there is a prefix set to all commands directed to the method exec
 Path - this is just an init parameter passed to the exec environment as a PATH. However, this must be run unpacked somewhere in the filesystem
 ENV_ - initParameter that starts with ENV_ is used to point to an environment variable with the name stripped of theleading ENV_ and using the init parameter value


 This class implements the Filter interface that is called by the web container. It acts as a decoder of the mulitpart/form-data stream sent by a HTML form that utilizes a file input item. Any files that is sent are stored to a temporary location and there will be a file object added to the request which will act as an attribute. It is made available that other values through the usual getParameter API and the setCharacterEncoding mechanism is respected when converting bytes to Strings.


 This is a simple servlet which extends the abstract class HttpServlet that displays the code 500 error message "JSP support not configured."


 This is an experimental servlet which implements the Servlet interface. It acts as an authorized servlet on behalf on another running servlet. This seems not to be a substitute for the running servlet but provides a mirror for the service.


 Implemented by the Filter interface, the ThrottlingFilter servlet concern is to protect a web application from having to handle an unmanageable load. This accounts when there is a server that holds one application with standardized resource restrictions and with this will be controlled by lowering or limiting the size of the ThreadPool. But when there are several applications in service or a single app having different resource requirements to different URLs, then the ThrottlingFilter comes in and guiding the number of requests being handled by Jetty.



 maximum - determines the maximum number of requests that may be on the filter chain anytime
 block - determines how long (in milliseconds) a request will be queued before it is rejected. Setting this to -1 blocks indefinitely
 queue - determines how many requests can be queued simultaneously and any additional requests will be rejected. Setting this to 0 turns off queueing


 This is another serlvet which also implements the Filter interface. This forwards any servlets to the necessary welcome display of an application when serviced.


 Found in the org.mortbay.jetty.servlet package, this servlet implements the ResourceFactory interface and extends the HttpServlet abstract class. This is the default servlet of Jetty usually mapped to / provides handling for static content, OPTION and TRACE methods for the    context. The MOVE method is allowed if PUT and DELETE are allowed.


Contact the core Jetty developers at
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 from 1 day to full product delivery