From f2f63334e98d93cef115a6e0b40f8ff8da5606fb Mon Sep 17 00:00:00 2001
From: markt All commands that the Manager application knows how to process are
specified in a single request URI like this: where Upload the web application archive (WAR) file that is specified as the
@@ -343,7 +343,7 @@ has been deployed using the {host} and {port} represent the hostname
and port number on which Tomcat is running, {command}
@@ -270,7 +270,7 @@ version of the messages.tag attribute. Note that the work
directory for the manager webapp will contain the previously deployed WARs;
removing it would make the deployment fail.
/path/to/foo on the Tomcat server is deployed as the
web application context named /footoo.
/foo. Notice
that the context path used is the name of the web application directory.
/bar.
Here is an example of deploying an application using a Context
configuration ".xml" file.
List the context paths, current status ( Signal an existing application to shut itself down and reload. This can
@@ -608,7 +608,7 @@ error message. Possible causes for problems include: Lists information about the Tomcat version, OS, and JVM properties.running or
@@ -549,7 +549,7 @@ OK - Listed applications for virtual host localhost
List the global JNDI resources that are available for use in resource @@ -680,7 +680,7 @@ include an error message. Possible causes for problems include:
List the security role names (and corresponding descriptions) that are @@ -733,7 +733,7 @@ include an error message. Possible causes for problems include:
Display the default session timeout for a web application, and the
@@ -753,7 +753,7 @@ Default maximum session inactive interval 30 minutes
Signal a stopped application to restart, and make itself available again.
@@ -796,7 +796,7 @@ error message. Possible causes for problems include: Signal an existing application to make itself unavailable, but leave it
@@ -839,7 +839,7 @@ error message. Possible causes for problems include: WARNING - This command will delete any web
@@ -928,7 +928,7 @@ file might look something like this:
- You will need to add manager role to the config file listed above. - For example: + For example, to add the manager role to a user named + tomcat with a password of s3cret, add the following to the + config file listed above.
<role rolename="manager"/> <user username="tomcat" password="s3cret" roles="manager"/>
+ Note that for Tomcat 7 onwards, the roles required to use the manager + application were changed from the single manager role to the + following four roles. You will need to assign the role(s) required for + the functionality you wish to access. +
For more information - please see the Manager App HOW-TO.
diff --git a/webapps/manager/404.jsp b/webapps/manager/404.jsp new file mode 100644 index 000000000..661bb67ae --- /dev/null +++ b/webapps/manager/404.jsp @@ -0,0 +1,59 @@ + +<%@ page import="org.apache.catalina.util.RequestUtil" %> + + ++ The page you tried to access + (<%=RequestUtil.filter((String) request.getAttribute( + "javax.servlet.error.request_uri"))%>) + does not exist. +
++ The Manager application has been re-structured for Tomcat 7 onwards and some + of URLs have changed. All URLs used to access the Manager application should + now start with one of the following options: +
+ You probably need to adjust the URL you are using to access the Manager + application. However, there is always a chance you have found a bug in the + Manager application. If you are sure you have found a bug, and that the bug + has not already been reported, please report it to the Apache Tomcat team. +
+ + diff --git a/webapps/manager/WEB-INF/web.xml b/webapps/manager/WEB-INF/web.xml index a067f212c..ff19a2071 100644 --- a/webapps/manager/WEB-INF/web.xml +++ b/webapps/manager/WEB-INF/web.xml @@ -27,12 +27,6 @@ Manager lets you view, load/unload/etc particular web applications. -