Table of Contents
This chapter discusses various options for configuring Jetty contexts.
The context path is the prefix of a URL path that Jetty uses to select the web application to which it routes
an incoming request. Typically a URL in a Java servlet server is of the format
http://hostname.com/contextPath/servletPath/pathInfo
, where each of the path elements can be zero or more
/ separated elements. If there is no context path, the context is referred to as the
root context.
How you set the context path depends on how you deploy the web application (or ContextHandler):
If you run Jetty from code as an embedded server (see ???), setting the context path
is a matter of calling the setContextPath
method on the ContextHandler
instance (or
WebAppContext
instance).
If you deploy the web application/context by Using the Context Provider, you set the
contextPath within the context.xml
file.
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Set name="contextPath">/foo</Set>...</Configure>
If you deploy the web application by Using the WebApp Provider, by default the name of the WAR
file forms the context path. So if the filename is foobar.war
, the context path is
/foobar
. There is a special case for webapps called root.war
which are mapped to
the root / context. See Setting Context Path to / (root).