You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by rj...@apache.org on 2014/09/21 16:31:04 UTC
svn commit: r1626582 - /tomcat/jk/trunk/xdocs/reference/apache.xml
Author: rjung
Date: Sun Sep 21 14:31:03 2014
New Revision: 1626582
URL: http://svn.apache.org/r1626582
Log:
Clarify semantics of JkMount and JkUnMount inside
a Location block.
Modified:
tomcat/jk/trunk/xdocs/reference/apache.xml
Modified: tomcat/jk/trunk/xdocs/reference/apache.xml
URL: http://svn.apache.org/viewvc/tomcat/jk/trunk/xdocs/reference/apache.xml?rev=1626582&r1=1626581&r2=1626582&view=diff
==============================================================================
--- tomcat/jk/trunk/xdocs/reference/apache.xml (original)
+++ tomcat/jk/trunk/xdocs/reference/apache.xml Sun Sep 21 14:31:03 2014
@@ -138,9 +138,14 @@ A mount point from a context to a Tomcat
<br/>
This directive is allowed multiple times.
It is allowed in the global configuration and in VirtualHost.
+<br/>
You can also use it inside Location with a different syntax.
Inside Location, one omits the first argument (path),
-which gets inherited from the Location.
+which gets inherited verbatim from the Location argument.
+Whereas <Location /myapp> matches any URI beginning with
+"/myapp", any JkMount nested in such a Location block will
+only match for requests with exact URI /myapp. Therefore nesting
+JkMount in Location is typically not the right thing to do.
<br/>
By default JkMount entries are not inherited from the global
server to other VirtualHosts or between VirtualHosts.
@@ -159,9 +164,15 @@ it will not be forwarded to tomcat, and
<br/>
This directive is allowed multiple times.
It is allowed in the global configuration and in VirtualHost.
+<br/>
You can also use it inside Location with a different syntax.
Inside Location, one omits the first argument (path),
-which gets inherited from the Location.
+which gets inherited verbatim from the Location argument.
+Whereas <Location /myapp> matches any URI beginning with
+"/myapp", any JkUnMount nested in such a Location block will
+only match for requests with exact URI /myapp. Therefore nesting
+JkUnMount in Location is typically not the right thing to do.
+<br/>
For inheritance rules, see: JkMountCopy.
<br/>
This directive is available in jk1.2.7 version and later.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org